As of exim-4.20-r1.ebuild the option to log to syslog has been removed. Can we please have it back? Reproducible: Always Steps to Reproduce: 1.emerge /usr/portage/net-mail/exim/exim-4.20-r1.ebuild 2./etc/init.d/exim restart 3.tail /var/log/messages Actual Results: I get no messages from exim Expected Results: I should see messages from exim This is the one thing I hate about Gentoo. Ebuild mantainers decide that functionality should change. If someone objects to logging to syslog then please add a keyword to kae it optional but functionality like this should not change on a whim. Thanks, =C=
As a work around add the following line to your exim.conf file: log_file_path=syslog A local USE variable will be added to support setting this option at compile time
*** Bug 28866 has been marked as a duplicate of this bug. ***
handing these over to Jay
This is NOTABUG and should be closed. Thanks. S.
I've got to disagree. It is a bug. This was normal behavior up through the 4.14 ebuild. Then somebody changed it. It broke scripts I run. Since it was the default behavior, if somebody doesn't like it, why not add a local keyword to change it but leave it as default for those of us who do like it? =C=
That's fair comemnt. I got hit by the same problem. I just assumed that publishing the information was sufficient. But I agree with the previous poster.
The /etc/exim/exim.conf.dist in exim 4.31.ebuild and onwards should now define log_file_path=syslog by default. # Note: # If exim cannot log to syslog it will try to log to, /var/log/exim/exim_%s.log log_file_path=syslog This should resolve this bug.
no more complaints/comments, marking bug resolved. feel free to re-open if there's still a problem.
This isn't resolved, as noted both in the duplicate bug report and the exim documentation there are situations in which exim logs only according the build instructions and not according to the conf file (basically when it panics on startup). The only correct resolution to this bug is a local USE variable as stated by Tim Schafer in the first comment. My apologies for not commenting on this before Colin closed it, I assumed Tim's resolution would be followed so I haven't been tracking it (I've been manually editing my exim ebuilds to 'correct' the log path). I don't have the power to reopen this.
O.K. I'll re-open this bug. a few points. I'll be adding a local USE variable called syslog, this will basically set the default (encoded into the binary) log bath to syslog, as this is a new local USE variable I don't believe it will affect anyone who's upgrading. I will disagree with the original bug that the option to log to syslog has been removed, for some reason it appears that the binary's log path was changed, the option is still there though. I don't know when this USE variable will be added, but I suspect it will be done by/at the time of the next exim version bump. Colin.
Added support to exim-4.43-r2 upwards
no further comments, ebuild has been in portage and stable for a while.
