Package: postgrey
Version: 1.34-1.3
Severity: normal
Dear Maintainer,
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
/etc/init.d postgrey stop
* What was the outcome of this action?
Log reports "Couldn't unlink "/var/run/postgrey.pid" [Permission denied]"
* What outcome did you expect instead?
No error.
Most likely the pid file should be in a directory that the user postgrey can
modify (such as /var/run/postgrey/postgrey.pid) rather than
/var/run/postgrey.pid, since /var/run is not writable by postgrey.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.13.7-x86_64-linode38 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages postgrey depends on:
ii adduser 3.113+nmu3
ii debconf [debconf-2.0] 1.5.52
ii libberkeleydb-perl 0.53-1+b1
ii libnet-dns-perl 0.68-1.2
ii libnet-server-perl 2.007-3
ii perl 5.18.2-2+b1
ii ucf 3.0027+nmu1
Versions of packages postgrey recommends:
ii libnet-rblclient-perl 0.5-2
ii libparse-syslog-perl 1.10-2
ii postfix 2.10.2-1
postgrey suggests no packages.
-- debconf information:
postgrey/1.32-3_changeport:
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
