[exim-dev] [Bug 2595] Allow custom socket path for SYSLOG
https://bugs.exim.org/show_bug.cgi?id=2595 Jeremy Harris changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #4 from Jeremy Harris --- Lacking further discussion, won't-fix. -- 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/ ##
[exim-dev] [Bug 2595] Allow custom socket path for SYSLOG
https://bugs.exim.org/show_bug.cgi?id=2595 --- Comment #3 from Jeremy Harris --- That's not gong to work, though. "syslogd", the one true original one, reads log items from the kernel. So if you're about to try and use some lash-up, you need to specify it. Most people would be using the syslogd facilities to split out the *output* side and direct it your chosen remote; I'm unconvinced this would be used by enough people to be worth the development and maintenance effort. -- 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/ ##
[exim-dev] [Bug 2595] Allow custom socket path for SYSLOG
https://bugs.exim.org/show_bug.cgi?id=2595 --- Comment #2 from Mike Rochford --- The environment is scaled globally where we have roughly 50+ Exim instances accepting email to relay to the internet. All push the logs to a distributed log collection service. The local log files are never used for log search as the retention is very short. Having a way to configure a private Syslog daemon would allow for all custom configurations to the Syslog daemon without interfering with the operating systems logging daemon. -- 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/ ##
[exim-dev] [Bug 2595] Allow custom socket path for SYSLOG
https://bugs.exim.org/show_bug.cgi?id=2595 --- Comment #1 from Jeremy Harris --- Justification needed: why the usual log files don't work for you. Also, any work done on this would need a specification for the comms to this "private syslog daemon". -- 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/ ##
