[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#591791: [PATCH] Document generic and upstart-specific init-system requirements



On 16.03.2012 21:25, Michael Biebl wrote:

> Personally, I would just prefer, if the shell library would forward the
> action requests to the native init system.

I still like this part of the original upstart-job idea (Steve knows the
details), simply because admins are used to the
/etc/init.d/<service> <action>
interface. Muscle memory and all.

Where the upstart-job idea failed, was the idea, that we could get away
without sysv init scripts (on Debian). It is obvious, that this won't
happen anytime soon.

For those who don't know upstart-job:
In Ubuntu, packages which ship a native upstart job foo, have a symlink
/etc/init.d/foo → /lib/init/upstart-job

If you type /etc/init.d/foo <action>
upstart-job will translate those requests into "initctl <action> foo".

What I would do differently nowadays, is change the way this works:
Packages continue to ship a sysv init script
If they ship a native upstart (or systemd) service file, they source a
shell library, which redirect those requests to the native service.

Currently we do that in systemd by (ab)using /lib/lsb/init-functions
which is a hack, so I'd like to do that properly.

Michael

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

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: