Could one or more of our Debian experts please comment on this, and
perhaps provide a patch to our contrib start/stop scripts if such is
warranted?
-MSK
---------- Forwarded message ----------
Date: Tue, 09 Oct 2012 01:31:29 -0700
From: SourceForge.net <noreply_at_sourceforge.net>
To: SourceForge.net <noreply_at_sourceforge.net>
Subject: [ opendkim-Bugs-3575666 ] Should kilproc be called with -p option?
Bugs item #3575666, was opened at 2012-10-09 01:31
Message generated for change (Tracker Item Submitted) made by
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1147701&aid=3575666&group_id=269812
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Packaging
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: cwolfhugel ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Should kilproc be called with -p option?
Initial Comment:
On Debian (and maybe others), killproc can take a -p option to specify the location of the pidfile. If unspecified, LSB assumes it is located in /var/run. When opendkim is run under a non privileged UID (-u option), it gives up privileges before creating the PID file, so it cannot be put in /var/run. The "stop" from the generic init script won't work as it always tried to get /var/run/opendkim.pid. Change would be to add "-p $PIDFILE" to ods_killproc. Need to check if it would break the self provided function.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1147701&aid=3575666&group_id=269812
Received on Tue Oct 09 2012 - 19:12:41 PST