I did figure out what the accept problem was, and it wasn't launchd
related. At this point everything seems to be working well.
On Apr 25, 2006, at 8:17 AM, Dave Zarzycki wrote:
Also please please please don't ever assume that only one socket is
in the array. I really want system administrators to feel that they
can add additional socket declarations to jobs and "everything
should just work (TM)." :-)
I'm not sure that I agree with this in every case. If a daemon is
listening on a particular socket, and the framework used to write an
app that uses this daemon also uses a particular socket, then the
admin really shouldn't be messing with it. I'd guess you're talking
about the case where they want the daemon to be listening to an
additional socket... Not a lot of justifiable reasons for doing
that, but I'll look at modifying the code to handle it.
Changing parameters for the heck of it is never a good idea.
The one question left is related to launchd messages. Sampled uses
exactly one. LAUNCH_KEY_CHECKIN. It doesn't show any examples of,
e.g., LAUNCH_KEY_STARTJOB, LAUNCH_KEY_STOPJOB, etc. Are any of the
other messages in launch.h of potential interest to a daemon, or are
they for internal use only? The comment in the header says that
calling launch_msg() with no message is a way to receive
asynchronous messages. Polling this seems clunky... Is there a way
to register a callback for asynchronous messages? Are there any
asynchronous messages I should be looking for?
Kevin
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-dev/email@hidden
