Re: Two line init.d scripts? Sure, that will work!
On 02/06/2014 10:56, Helmut Grohne wrote:
> The relevant bits can be found in insserv, watch out for
> "/lib/init/upstart-job".
The current version of insserv in unstable, 1.14.0-5, doesn't seem to
contain this file.
> It takes things one step further though.
> Instead of having an interpreted script, it right out replaces the init
> script with a symbolic link to the mentioned helper. That in turn can
> derive the job name from argv[0] and use the existing upstart job
> description.
>
> My attempt to reproduce such a utility for systemd have not worked out
> unfortunately (for lack of time/interest).
Using systemd jobs instead of the init script if available is already
implemented:
~ # /etc/init.d/cron restart
[ ok ] Restarting cron (via systemctl): cron.service.
> Why not write an upstart job instead? It works with sysvinit today!
How would the init script continue to work on sysvinit if it was
replaced with a symlink as you said earlier?
Ansgar
Reply to: