[MacPorts] #26345: syslog-ng respawn attempts until pid type changed and pidfile added
MacPorts
noreply at macports.org
Tue Sep 7 09:52:26 PDT 2010
#26345: syslog-ng respawn attempts until pid type changed and pidfile added
---------------------------------+------------------------------------------
Reporter: sgilmer50@… | Owner: markd@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.9.1
Keywords: | Port: syslog-ng
---------------------------------+------------------------------------------
Comment(by sgilmer50@…):
Replying to [comment:2 markd@…]:
> Maybe it needs this added:
>
> startupitem.pidfile auto --pidfile=${prefix}/var/syslog-ng.pid
>
> I'm not clear on whether "auto" or "clean" option is correct, I would
think "clean".
I think you're right about adding startupitem.pidfile. I tested using
both auto and clear by changing the startup plist with --pid=fileauto and
fileclean and both seemed to work. For both tests I did a 'port unload
syslog-ng', modified the plist, and then 'sudo port load syslog-ng' and
then killed the syslog-ng process. In both cases syslog-ng was restarted
and did logging successfully. I'm guessing that auto works because
syslog-ng probably gets rid of an old pid file if it exists.
--
Ticket URL: <http://trac.macports.org/ticket/26345#comment:3>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list