Bug#880047: closed by Peter Palfrader (Re: Bug#880047: postgrey doesn't start because it can't write its pid)

On Wed, May 15, 2019 at 08:12:07AM +, Debian Bug Tracking System wrote: > It seems to me that the default init script that ships with Debian 9 > does not use the directory /var/run/postgrey. postgrey/1.36-3+deb9u2 has worked just fine for me on Debian 9. I didn't experience any problems relate

Bug#880047: postgrey doesn't start because it can't write its pid

Hi, I triaged this bug on a fresh stretch VM. Installing postgrey 1.36-3 and rebooting did not trigger the bug. I tried with both systemd and sysvinit. Looking at /etc/init.d/postgrey, I see the following: PIDFILE=/var/run/$DAEMON_NAME.pid So the above init script shipped in stretch does not req

Bug#880047: postgrey doesn't start because it can't write its pid

Package: postgrey Version: 1.36-3 Severity: grave Justification: renders package unusable Dear Maintainer, The default init script that comes with Postgrey on Debian 9 fails to start after a reboot. The installer creates /var/run/postgrey and writes its pid there but /var/run is a tmpfs file sy