[MacPorts] #26345: syslog-ng respawn attempts until pid type changed and pidfile added

[MacPorts]

#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:4 markd@…]:
 > Ok, I added the --pidfile with 'clean' option on revision 1 of the
 portfile.  Seems like maybe that is a safer option?  The guide is wrong
 about --pidfile (and other options?) for startupitem.executable type -that
 it isn't needed or can't be used or whatever.  I wrote it so it is my
 fault, but that is what I thought at the time.  If the revision looks ok
 to you I can close the ticket.  Thanks for the detailed reporting and
 testing on this.

 The resulting plist from revision 1 ends up with two --pidfile lines.  One
 with just '--pidfile' and another with '--pidfile=/opt/local/var/syslog-
 ng.pid'.  This causes an attempted restart of syslog-ng about every 30
 sec. Also, daemondo isn't running. Removing the line with just '--pidfile'
 fixes the problem.

 Looking at the documentation a little closer, it looks like
 startupitem.pidfile can't be used with executable type startupitems.  I
 wonder whether the port file without specifying startupitem.pidfile would
 work if syslog-ng placed it's pid file in ${prefix}/var/run rather than
 ${prefix}/var.  I can't think of anything else that might work.

-- 
Ticket URL: <http://trac.macports.org/ticket/26345#comment:6>
MacPorts <http://www.macports.org/>
Ports system for Mac OS