On Sun, Jan 27, 2008 at 12:01:57AM +0100, Bernd Zeimetz wrote:
> This bug introduce a serious risk of loosing important log data, which
> is - especially for a MTA - not acceptable. Asking people to restart
> postfix after reloading syslog is a *stupid* workaround, which also
> results in the loss of log entries (during the time when syslog is
> restarted but postfix not yet). The only working, but not less ugly,
> workaround is to stop postfix first, then reload/restart syslog, and
> start postfix again.
The only long-term workable solution to this bug is for syslog to allow
postfix to specify an alternate socket.
> It seems you're just doing nothing to fix this bug, this behavior is a
> shame as you're ruining the image of postfix as the best MTA we have in
> Debian. If you really think the bug should be fixed in sysklogd -
> where's the open grave bug in sysklogd, syslog-ng and other syslog
> daemons which block *this* bug?
Cloned and filed, as anyone could have done. Tracking down how to do
that took me a little while, as I've not done it previously.
> There're a few ways to get a syslog socket into the chroot, like
> - using syslog-ng: my suggested way, but depending on a syslog daemon is
> not nice.
> - using bind mounts: not available on older kernels, also a bind mount
> needs to be recreated after re{loading,starting} the syslog daemon
3) change /etc/default/syslog to say
SYSLOG="-a /var/spool/postfix/dev/log"
and then rsync -av /dev/log /var/spool/postfix/dev/log
Note that any admin can do that, postfix may not edit the config file of
another package.
lamont
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
