Control: tag -1 + confirmed
Hi,
Andreas Metzler wrote:
FYI this totally broke greylisting for me after upgrading to wheezy
and migrating to a new server as
service postgrey restart
did not restart the daemon and therefore did not apply the
configuration changes I made which were necessary
Control: found -1 1.34-1.2
Axel Beckert wrote:
[...] can confirm the issue. :-)
... in Wheezy as well as in Jessie and Sid.
Regards, Axel
--
,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' |
Hi,
Nye Liu wrote:
/etc/init.d/postgrey passes --name to start-stop-daemon, but start-stop-daemon
apparently expects a full path (/usr/sbin/postgrey vs postgrey)
However, start-stop-daemon is also limited to 15 characters
So stop/reload do NOT work at all.
Yes. That's the core of the
Control: severity 670681 serious
Hello,
FYI this totally broke greylisting for me after upgrading to wheezy
and migrating to a new server as
service postgrey restart
did not restart the daemon and therefore did not apply the
configuration changes I made which were necessary for a working
It seems like the start-stop-daemon uses /proc/pid/stat to find the
matching process name like 'pgrep' does it.
The man page of 'pgrep' describes the limitation:
NOTES
The process name used for matching is limited to the 15 characters
present in the output of /proc/pid/stat.
Use the -f option to
The patch supplied by Nye Liu fixes this issue for me on a system
running Debian stable (wheezy). However, on another system which is
updated to Debian testing (jessie) the startup script does not work at
all - it just prints green [ok] but postgrey is actually not started!
--
To UNSUBSCRIBE,
Package: postgrey
Version: 1.34-1.1
Followup-For: Bug #670681
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
Patch did not work for me. What worked was this change of init script:
# line 80 - replaced
--pidfile $PIDFILE --name $SSNAME
# with
--pidfile
The patch supplied by Nye Liu fixes this issue for me, too.
# dpkg -l | grep postgrey
ii postgrey 1.34-1.1 all greylisting implementation for Postfix
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
I can verify that this patch has resolved my ability to reload postgrey
after upgrading from Squeeze to Wheezy. (Thanks, Nye Liu!) It'd be great
to see this patch get accepted (or this bug otherwise fixed, if the
package maintainers know of a more correct way to resolve the issue).
--
To
Package: postgrey
Version: 1.34-1.1
Severity: important
Tags: patch
/etc/init.d/postgrey passes --name to start-stop-daemon, but start-stop-daemon
apparently expects a full path (/usr/sbin/postgrey vs postgrey)
However, start-stop-daemon is also limited to 15 characters
So stop/reload do NOT
10 matches
Mail list logo
