You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4cxx-dev@logging.apache.org by "Rhys Ulerich (JIRA)" <lo...@logging.apache.org> on 2014/10/21 14:16:33 UTC

[jira] [Commented] (LOGCXX-442) Using non standard ports with syslog

    [ https://issues.apache.org/jira/browse/LOGCXX-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14178330#comment-14178330 ] 

Rhys Ulerich commented on LOGCXX-442:
-------------------------------------

As I'm not familiar with that portion of the codebase, is there some other configuration option that behaves the way you'd like to syslog port to behave?  That'll let me see if mimicking that other option will do what you need.

> Using non standard ports with syslog
> ------------------------------------
>
>                 Key: LOGCXX-442
>                 URL: https://issues.apache.org/jira/browse/LOGCXX-442
>             Project: Log4cxx
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 0.10.0
>         Environment: Windows 2012
>            Reporter: nov1ce
>            Priority: Minor
>
> Hello,
> Would it be feasible to add a possibility to use non standard ports with syslog, either by specifying the :port at the SyslogHost part, or via additional parameter (for example: <param name="Port" value="XXX" />?
> It looks like it's hardcoded to 514/udp right now:
> syslogwriter.cpp:
> #define SYSLOG_PORT 514
> Thank you.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)