http://bugzilla.novell.com/show_bug.cgi?id=519438
Summary: Postfix: Running chrooted lets qmgr loosing his
syslog-socket
Classification: openSUSE
Product: openSUSE 11.1
Version: Final
Platform: i586
OS/Version: openSUSE 11.1
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Network
AssignedTo: bnc-team-screening@forge.provo.novell.com
ReportedBy: p.heinlein@jpberlin.de
QAContact: qa@suse.de
Found By: ---
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.0.7)
Gecko/2009022800 SUSE/3.0.7-1.1.6 Firefox/3.0.7
Setting up a chroot-enviroment in Postfix (/etc/sysconfig/postfix) leads to a
chrooted qmgr-process in /etc/postfix/master.cf.
This is working at the beginning, because qmgr opens his socket to syslog
before becoming chrooted.
After restarting Syslog (or using logrotate due to a cron-job) the
syslog-socket gets lost and qmgr isn't available to reopen it -- because qmgr
is now chrooted.
There are two ways to solve that:
*) Adding a second syslog-socket under /var/spool/postfix/...
*) Do not use chroot for qmgr (recommended by Wietse Venema himself)
If the syslog-socket gets lost Postfix is just able to log some, but not ALL
necessary informations about the e-mail-traffic. Especially important log-lines
like "from=