The init script of postgrey claims: # processname: postgrey # pidfile: /var/run/greylist.pid but postgrey does not create this pid file by default and no --pidfile option is given (neither in the init script nor in /etc/sysconfig/postgrey). Thus systemd thinks the service is failed when in fact it is running: postgrey[12588]: Starting postgrey:[ OK ] systemd[1]: PID file /var/run/greylist.pid not readable (yet?) after start. systemd[1]: postgrey.service operation timed out. Terminating. systemd[1]: Unit postgrey.service entered failed state. $ systemctl status postgrey.service postgrey.service - LSB: Starts the postfix Greylisting Policy Server Loaded: loaded (/etc/rc.d/init.d/postgrey) Active: failed (Result: timeout) since Sat, 19 May 2012 16:50:55 +0200; 27min ago Process: 12588 ExecStart=/etc/rc.d/init.d/postgrey start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/postgrey.service รข 12645 /usr/sbin/postgrey -d --unix=/var/spool/postfix/ex...
Keywords: (none) => Junior_jobAssignee: bugsquad => misc
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
I reported the bug shortly before the release of Mageia 2 and haven't seen an update yet so I assume it's still valid. There's more than one possible way to fix this, I attach a workaround I'm using now.
Created attachment 2401 [details] Add --pidfile option to /etc/sysconfig/postgray
Attachment 2401 is patch: 0 => 1 Attachment 2401 mime type: application/octet-stream => text/plain
Keywords: NEEDINFO => (none)CC: (none) => sander.lepikWhiteboard: (none) => MGA2TOO
*** This bug has been marked as a duplicate of bug 6392 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE