[EMAIL PROTECTED] wrote:
i Mark,
So it looks like the bit magic that got this to work is the -f
command, which basically tells dhcpd not to daemonize, which would be
a good thing in our case, as the process of daemonizing would look to
daemondo or launchd as if dhcpd were exiting, which would ca
>i Mark,
>
>So it looks like the bit magic that got this to work is the -f
>command, which basically tells dhcpd not to daemonize, which would be
>a good thing in our case, as the process of daemonizing would look to
>daemondo or launchd as if dhcpd were exiting, which would cause the
>constantly r
Hi guys,
I put dhcp back to the startupitem.executable but using -f.
The port's name is dhcp and the daemon's name is dhcpd, so startupitem.name is
needed.
Regards,
Blair
James Berry wrote:
Hi Mark,
So it looks like the bit magic that got this to work is the -f command,
which basically te
Hi Mark,
So it looks like the bit magic that got this to work is the -f
command, which basically tells dhcpd not to daemonize, which would be
a good thing in our case, as the process of daemonizing would look to
daemondo or launchd as if dhcpd were exiting, which would cause the
constantl
>Mark,
>
>It works fine if I use this:
>
>startupitem.create yes
>startupitem.name dhcpd
>startupitem.executable ${prefix}/sbin/dhcpd -f
>startupitem.netchange yes
>
>How's that?
The startupitem executable is preferred if it works automatically I think;
but if it doesn't for some re
Blair,
I see. That's fine then. I just wanted to be sure there was a reason for
making it a script startupitem and there is. I'm cc'ing James (master of
all things startupitem) just in case he knows why the executable
startupitem type wasn't adequate in this case. It seems like it should
have
Mark,
It works fine if I use this:
startupitem.create yes
startupitem.namedhcpd
startupitem.executable ${prefix}/sbin/dhcpd -f
startupitem.netchange yes
How's that?
Regards,
Blair
On Jan 13, 2008, at 12:36 PM, Blair Zajac wrote:
Hi Mark,
The guild says this:
"startupitem.e
Hi Mark,
The guild says this:
"startupitem.executable. Specifies the name of the daemon to be run
in the background. It may have multiple arguments, but they must be
appropriate for a call to exec; arbitrary shell code may not be used."
Should the actual daemon remain in the foreground so
Hi Mark,
I was seeing the following:
1) One dhcpd would start.
2) Every 10 seconds thereafter, another dhcpd would be started, but it
couldn't bind to the port since the first one was running.
It appears that the startupitem infrastructure wasn't keeping track of
dhcpd running and deamoni
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
revertin
10 matches
Mail list logo
