[exim-dev] [Bug 2595] Allow custom socket path for SYSLOG

2020-06-21 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2595 Jeremy Harris changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[exim-dev] [Bug 2595] Allow custom socket path for SYSLOG

2020-06-09 Thread admin--- via Exim-dev
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

[exim-dev] [Bug 2595] Allow custom socket path for SYSLOG

2020-06-09 Thread admin--- via Exim-dev
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

[exim-dev] [Bug 2595] Allow custom socket path for SYSLOG

2020-06-09 Thread admin--- via Exim-dev
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