Control: tag -1 + moreinfo unreproducible On Sun, 24 Jun 2012 14:06:24 +0200 Toni Mueller <supp...@oeko.net> wrote:
Dear Maintainer, on my Testing system, the generated start sequence is S10rsyslog S20postfix
That's correct. Postfix should be started only after syslogd socket (/dev/log) is ready.
Now, when rsyslog starts, there is no socket as specified in /etc/rsyslog.d/postfix.conf, since Postfix hasn't started yet. Therefore, rsyslogd doesn't notice when Postfix starts and creates the socket (I think that the old syslogd wouldn't listen, either). Therefore, I think it is necessary to HUP the syslogd-du-jour on Postfix start, and maybe also on Postfix stop when the socket goes away, in order to make logging work.
And here you got it all exactly backwards. It is not postfix who creates the socket, - postfix will *use* a socket created by rsyslogd. And in order for postfix to use that socket, rsyslogd has to create the socket before postfix is started. Actually, the socket in /var/spool/postfix/dev/log is sort of optional - it is only needed if you *restart* your syslogd when postfix is running, so postfix loses connection with syslogd, and tries to re-open /dev/log (in postfix chroot this time). So if your rsyslogd does not create socket in /var/spool/postfix with the /etc/rsyslog.d/postfix.conf provided by postfix, it is a bug in rsyslogd. Let's keep this bug open for a little more to allow possible response, but I'd close it right away. /mjt
