Upstart 0.5 Are We There Yet?

[Michael Biebl]

Hi Scott,

thanks for keeping us updated!

2008/1/16, Scott James Remnant <scott at netsplit.com>:
>
> [NEW] Service readiness announcement through SIGSTOP.
>
>         When services remain in the foreground, there's no usual
>         way for them to signal that they have completed their
>         initialisation and are ready to receive client connections.
>
>         The usual method when they go into the background is to use the
>         fork() for this, but obviously this isn't available.
>
>         Upstart supports a different method for foreground services,
>         they may raise the SIGSTOP signal.  This signals that they are
>         ready, Upstart will sent them SIGCONT and adjust its own job
>         state to take the job out of SPAWNED and towards RUNNING.

Do you use a new flag in the job description file to signal if you
have to wait for SIGSTOP? If not, how do you differentiate non-forking
jobs that use SIGSTOP from the ones which don't?


> Disable a job from its definition, instead of just deleting it.
>
>         I have again become unconvinced of the usefulness of this,
>         instead favouring something more like "profiles" or "flags"
>         where jobs can be disabled and enabled en-masse.
>
>         Unless somebody can provide a use-case for having a defined job
>         that cannot be started?


I can only speak from my own experience. E.g. I have apache2 installed
on it, but disabled it from starting at boot (I only need it on
special occasions and then I start it manually).
It's definitely possible to achieve that with profiles or flags, I
only think it would be more effort and less convenient.

Cheers,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?