I just ugpraded exim from 4.14 to 4.21, and exim is no longer syslogging anything. My syslog-ng configuration contains the following: source src { unix-stream("/dev/log"); internal(); pipe("/proc/kmsg"); }; destination everything { file("/var/log/everything"); }; destination console_all { file("/dev/tty12"); }; filter f_noncron { not facility(cron); }; log { source(src); destination(console_all); }; log { source(src); filter(f_noncron); destination(everything); }; ... so it really should be logging. The old exim logged. Is it possible that this is a problem with sandboxing when the new exim was built? This is doubtful because exim doesn't use configure. What is broken? Thanks. S.
Apparently the log files have moved to /var/log/exim and no longer go through syslog at all. Setting: log_file_path = syslog in exim.conf restores the original settings. This bug can be closed; perhaps a warning message somewhere in the ebuild would be good?
This problem makes exim log a panic to /var/log/mail/ and immediately exit when started by /etc/init.d/exim start. The init script just said [ok]. I think the ebuild should either change the sample configuration to use syslog or create the necessary /var/log/exim dir and chown it mail:mail.
*** This bug has been marked as a duplicate of 27206 ***
