ports/114106: mail/postgrey does not properly shut down via rc.d script

Jeremy Chadwick koitsu at FreeBSD.org
Thu Jun 28 18:20:03 UTC 2007


>Number:         114106
>Category:       ports
>Synopsis:       mail/postgrey does not properly shut down via rc.d script
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jun 28 18:20:02 GMT 2007
>Closed-Date:
>Last-Modified:
>Originator:     Jeremy Chadwick
>Release:        FreeBSD 6.2-STABLE i386
>Organization:
>Environment:
System: FreeBSD icarus.home.lan 6.2-STABLE FreeBSD 6.2-STABLE #0: Mon Jun 18 12:42:07 PDT 2007 root at icarus.home.lan:/usr/obj/usr/src/sys/ICARUS i386
>Description:
	It seems that postgrey doesn't shut down when using
	"/usr/local/etc/rc.d/postgrey stop", despite the pidfile containing
	the correct pid.
>How-To-Repeat:
	Example session:

eos# ls -l /var/run/postgrey.pid
ls: /var/run/postgrey.pid: No such file or directory
eos# /usr/local/etc/rc.d/postgrey start
Starting postgrey.
eos# ls -l /var/run/postgrey.pid
-rw-r--r--  1 postgrey  postgrey  6 Jun 28 10:52 /var/run/postgrey.pid
eos# cat /var/run/postgrey.pid
61665
eos# ps -auxw | grep 61665
postgrey 61665  0.0  0.3  8644  7920  ??  Ss   10:52AM   0:00.01 [perl5.8.8]
eos# /usr/local/etc/rc.d/postgrey stop
postgrey not running? (check /var/run/postgrey.pid).
eos# cat /var/run/postgrey.pid
61665
eos# ps -auxw | grep 61665
postgrey 61665  0.0  0.3  8644  7852  ??  Is   10:52AM   0:00.01 [perl5.8.8]

	Local configuration (rc.conf):

postgrey_enable="yes"
postgrey_pidfile="/var/run/postgrey.pid"
postgrey_flags="--pidfile=${postgrey_pidfile} --inet=10023 -d --user=postgrey --group=postgrey --dbdir=/var/db/postgrey --delay=180 --hostname=mx01.sc1.parodius.com --whitelist-clients=/conf/ME/postfix/postgrey_whitelist_clients --whitelist-recipients=/conf/ME/postfix/postgrey_whitelist_recipients"

>Fix:
	No idea.  The couple hacks I had in mind don't fix it.

>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the freebsd-ports-bugs mailing list