site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com It's usually straightforward for the daemon to vend the appropriate self-manipulation functionality; frequently you want to gate this with application-specific logic anyway. Why do you need 'stop'? Why can't you just ask the daemon to enter a state where it refuses requests? So just fix it and tell it to exit. -- Terry _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... On Apr 10, 2009, at 9:31 AM, Bill Janssen <janssen@parc.com> wrote: Michael Smith <drivers@mu.org> wrote: On Apr 9, 2009, at 9:30 AM, Bill Janssen wrote: Michael Smith <drivers@mu.org> wrote: Well, the daemon does a lot of things, but what I'm concerned with is stop, start, and restart. Because I want to fix it with new code. When a process exits and launchd restarts it, launchd doesn't know if it's running old code or new code when it's relaunched, it just knows its path. This email sent to site_archiver@lists.apple.com