https://bugs.exim.org/show_bug.cgi?id=2595
Bug ID: 2595
Summary: Allow custom socket path for SYSLOG
Product: Exim
Version: N/A
Hardware: x86
OS: All
Status: NEW
Severity: bug
Priority: medium
Component: Logging
Assignee: unallocated@exim.org
Reporter: michael.rochford@thomsonreuters.com
CC: exim-dev@exim.org
The current implementation of Syslog logging in Exim you are unable to point to
a custom socket to send to. The environment I am in an application owner has
limited configuration rights to the systems Syslog daemon. Operations recommend
that we run our own Syslog daemon in userspace. Based on the documentation
there is no way to point Exim to that daemon running in userspace.
I might be missing something from the documentation, or this might be an
awesome request.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
Bug ID: 2595
Summary: Allow custom socket path for SYSLOG
Product: Exim
Version: N/A
Hardware: x86
OS: All
Status: NEW
Severity: bug
Priority: medium
Component: Logging
Assignee: unallocated@exim.org
Reporter: michael.rochford@thomsonreuters.com
CC: exim-dev@exim.org
The current implementation of Syslog logging in Exim you are unable to point to
a custom socket to send to. The environment I am in an application owner has
limited configuration rights to the systems Syslog daemon. Operations recommend
that we run our own Syslog daemon in userspace. Based on the documentation
there is no way to point Exim to that daemon running in userspace.
I might be missing something from the documentation, or this might be an
awesome request.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##