Status of upstart in Debian?

Scott James Remnant scott at
Tue Apr 6 15:44:33 UTC 2010

On Tue, 2010-04-06 at 17:26 +0200, Michael Biebl wrote:

> I notice, that Ubuntu currently doesn't do it that way.
We don't support insserv, and we also don't support sysvinit (there is
no such package in Ubuntu)

For us, upstart-job is simply a shell script that retains
the /etc/init.d/foo symlinks sysadmins may be used to typing, and
teaches them the new thing to type.

> >> 2/ How do we ensure the correct ordering? Take the dbus/rsyslog example
> >> again. When can we start the legacy sysv rc2 stage and be sure that the
> >> upstart jobs are up?
> >>
> > The headers in the Upstart job provide the "alternate ordering" based on
> > runlevels.
> My question was, how do we ensure that native upstart jobs that are dependencies
> of legacy sysv init script are started before the sysv init scripts.
We don't allow that situation.

> >>>  - a system with sysvinit installed would use insserv to run both init
> >>>    scripts and Upstart jobs (via upstart-job)
> >>
> >> How do we implement the "status" and "stop" action for services, i.e.
> >> how do we get the pid?
> >>
> > Write a pid file.
> How exactly would you do that?
fp = fopen (PATH_TO_PID_FILE, "w");
fprintf (fp, "%d\n", pid);
fclose (fp);

> >> The other remaining requirements I can remember, which Petter had and we
> >> discussed during the sprint in London [1], was the inittab handling.
> >>
> > Ah yes, of course.
> Which of the two proposals do you prefer?
I don't mind

Scott James Remnant
scott at
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <>

More information about the initscripts-ng-devel mailing list