Hi Blair, Executable startupitems are the preferred type. Daemondo can track pids automatically and reliably restart an application if it quits. See the guide on this:
http://guide.macports.org/#reference.startupitems Given how startupitem executables work, I don't see an advantage to reverting to a "script" startupitem. Or is there something I am missing particular to dhcp? Mark >Log Message: >----------- >Use a startupitem method that uses dhcpd's PID file. >Modified Paths: >-------------- > trunk/dports/net/dhcp/Portfile > >Modified: trunk/dports/net/dhcp/Portfile >=================================================================== >--- trunk/dports/net/dhcp/Portfile 2008-01-13 03:07:29 UTC (rev >32750) >+++ trunk/dports/net/dhcp/Portfile 2008-01-13 03:35:29 UTC (rev >32751) >@@ -4,7 +4,7 @@ > > name dhcp > version 3.1.0 >-revision 1 >+revision 2 > categories net > description ISC dhcpd server > long_description ISC's Dynamic Host Configuration Protocol >Distribution \ >@@ -40,8 +40,9 @@ > configure.pre_args > > startupitem.create yes >-startupitem.name dhcpd >-startupitem.executable ${prefix}/sbin/dhcpd >+startupitem.start "${prefix}/sbin/dhcpd" >+startupitem.restart "/bin/kill -HUP \$(/bin/cat >${prefix}/var/run/dhcpd.pid)" >+startupitem.stop "/bin/kill -15 \$(/bin/cat >${prefix}/var/run/dhcpd.pid)" _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
