Re: testing the current bootstrap context?
Re: testing the current bootstrap context?
- Subject: Re: testing the current bootstrap context?
- From: Bill Janssen <email@hidden>
- Date: Fri, 10 Apr 2009 11:55:02 PDT
- Comments: In-reply-to Terry Lambert <email@hidden> message dated "Fri, 10 Apr 2009 10:34:52 -0700."
Terry Lambert <email@hidden> wrote:
> On Apr 10, 2009, at 9:31 AM, Bill Janssen <email@hidden> wrote:
> > Michael Smith <email@hidden> wrote:
> >> On Apr 9, 2009, at 9:30 AM, Bill Janssen wrote:
> >>> Michael Smith <email@hidden> wrote:
> >>>> 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.
> >>>
> >>> Well, the daemon does a lot of things, but what I'm concerned with
> >>> is
> >>> stop, start, and restart.
> >>
> >> Why do you need 'stop'? Why can't you just ask the daemon to enter a
> >> state where it refuses requests?
> >
> > Because I want to fix it with new code.
>
> So just fix it and tell it to exit.
>
> 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.
Sure, but the old code does bad things on exit (like saving state in an
invalid format). I'm pretty sure I need, in the general case, to be
able to stop it, fix things, and restart it.
Bill
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden