From dpelleg+@cs.cmu.edu  Fri Jan 14 18:39:44 2005
Return-Path: <dpelleg+@cs.cmu.edu>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2D74416A4CE
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 14 Jan 2005 18:39:44 +0000 (GMT)
Received: from gw.pelleg.org (gw.pelleg.org [205.201.13.235])
	by mx1.FreeBSD.org (Postfix) with ESMTP id DE21A43D2F
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 14 Jan 2005 18:39:43 +0000 (GMT)
	(envelope-from dpelleg+@cs.cmu.edu)
Received: from palraz.wburn (palraz [192.168.1.1])
	by gw.pelleg.org (Postfix) with ESMTP id 35F7E5A64
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 14 Jan 2005 13:39:42 -0500 (EST)
Received: by palraz.wburn (Postfix, from userid 7675)
	id 4A8AD1029; Fri, 14 Jan 2005 13:39:41 -0500 (EST)
Message-Id: <20050114183941.4A8AD1029@palraz.wburn>
Date: Fri, 14 Jan 2005 13:39:41 -0500 (EST)
From: Dan Pelleg <daniel+gnats@pelleg.org>
Reply-To: Dan Pelleg <daniel+gnats@pelleg.org>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: postgrey startup script failes to stop
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         76253
>Category:       ports
>Synopsis:       postgrey startup script failes to stop
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    vs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jan 14 18:40:23 GMT 2005
>Closed-Date:    Wed Feb 23 15:04:43 GMT 2005
>Last-Modified:  Wed Feb 23 15:04:43 GMT 2005
>Originator:     Dan Pelleg
>Release:        4.10-RELEASE-p5
>Organization:
>Environment:

4.10-RELEASE-p5


	
>Description:

One problem is that the pidfile /var/run/postgrey.pid isn't created. I tried to
make a directory /var/run/postgrey and make it owned by user postgrey. When I then
use the pidfile /var/run/postgrey/postgrey.pid it is created, so it's probably just
a permission problem.

Now, "/usr/local/etc/rc.d/postgrey.sh stop" still doesn't work. The reason
is that the process name does not match "postgrey". I think the process
is just perl.

>How-To-Repeat:
	

- install postgrey port.
- /usr/local/etc/rc.d/postgrey.sh start
- /usr/local/etc/rc.d/postgrey.sh stop

>Fix:

	


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: vs 
State-Changed-When: Mon Jan 17 15:41:02 GMT 2005 
State-Changed-Why:  
Forwarded PR to maintainer 

http://www.freebsd.org/cgi/query-pr.cgi?pr=76253 

From: "Volker Stolz" <vs@freebsd.org>
To: freebsd-gnats-submit@freebsd.org, daniel+gnats@pelleg.org,
	haroldp@internal.org
Cc:  
Subject: Re: ports/76253: postgrey startup script failes to stop
Date: Mon, 17 Jan 2005 16:40:49 +0100

 Dear maintainer, please look into this issue!
 
 Volker

From: Dan Pelleg <daniel+gnats@pelleg.org>
To: freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: ports/76253: postgrey startup script failes to stop
Date: Wed, 19 Jan 2005 11:41:52 -0500

 This seems to only be a problem if you can't access /dev/kmem, which
 happens to be the case for the jailed hosting provider here. 
 
 As far as I'm concerned, this PR can be closed.
Responsible-Changed-From-To: freebsd-ports-bugs->vs 
Responsible-Changed-By: vs 
Responsible-Changed-When: Wed Feb 9 15:37:55 GMT 2005 
Responsible-Changed-Why:  
Handle. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=76253 
State-Changed-From-To: feedback->closed 
State-Changed-By: vs 
State-Changed-When: Wed Feb 23 15:04:01 GMT 2005 
State-Changed-Why:  
Closed on submitter's request: Local issue, workaround found 

http://www.freebsd.org/cgi/query-pr.cgi?pr=76253 
>Unformatted:
