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 "Chand Priyankara (JIRA)" <lo...@logging.apache.org> on 2015/01/29 15:29:35 UTC

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

     [ https://issues.apache.org/jira/browse/LOGCXX-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chand Priyankara resolved LOGCXX-442.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.11.0
         Assignee: Chand Priyankara

Patched with the fix to make compatible with log4j, by providing the ability to specify the port with the address.
Credits to 'Ulrik' for the patch.

Trunk build successfully after patch.
Locally tested.

> 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
>            Assignee: Chand Priyankara
>            Priority: Minor
>             Fix For: 0.11.0
>
>         Attachments: syslogappenderport.patch
>
>
> 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)