Bug#311812: postfix: syslog reconnection - please provide, syslogd socket in jail

2008-01-27 Thread Martin Zobel-Helas
Hi, has anyone thought of having a look how other distributions solved this problem? I am pretty sure some might already have solved that problem. Greetings Martin -- Martin Zobel-Helas <[EMAIL PROTECTED]> | Debian Release Team Member Debian & GNU/Linux Developer | Debia

Bug#311812: postfix: syslog reconnection - please provide, syslogd socket in jail

2008-01-26 Thread LaMont Jones
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

Bug#311812: postfix: syslog reconnection - please provide, syslogd socket in jail

2008-01-26 Thread Bernd Zeimetz
severity 311812 grave #rationale: data loss tags 311812 + etch lenny sid thanks 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

Bug#311812: postfix: syslog reconnection - please provide syslogd socket in jail

2008-01-17 Thread LaMont Jones
severity 311812 important -- On Thu, Jan 17, 2008 at 04:17:12PM +, Alexander Wirt wrote: > severity 311812 grave It's only grave if the bug is against syslogd. Syslogd doesn't provide a method for postfix to change the config file, and therefore it would be a policy violation for postfix to

Bug#311812: postfix: syslog reconnection - please provide syslogd socket in jail

2008-01-17 Thread Alexander Wirt
severity 311812 grave thanks Hi, today I have been hit by this bug, which made logs from 3 days mostly useless. Asking on postfix-users about it gave me the following answer: Complain to your maintainer. The bug is that YOUR DISTRIBUTION uses Postfix chroot with an inco