On 19 May 2013 02:14, Steve Langasek <steve.langasek@ubuntu.com> wrote:
> Before forwarding upstart jobs, there are a few things to be aware of. The
> tl;dr version of this for those who just want to start fixing packages and
> forwarding patches can be found at
> <https://wiki.ubuntu.com/UpstartCompatibleInitScripts>.
>
I've converted a non-trivial scripts into upstart compatible scripts.
And I have a question about exact requirements behind:
"Make sure that the upstart jobs and init scripts in the package have
matching names. If the names do not match, either the init script
should be split (cf. /etc/init.d/samba->/etc/init.d{s,n}mbd in the
samba package), or dummy upstart jobs should be created (cf.
/etc/init/mountall.sh.conf in the mountall package) so that the names
line up. Without this, insserv will not correctly detect that the
upstart job has started and dependency-based booting will fail."
What are the exact requirements here? one-to-one matching?
For example in util-linux package there are:
- in debian: hwclock.sh init script
- in ubuntu: hwclock and hwclock-save upstart jobs
I have added the two upstart jobs and created an "dummy" hwclock.sh
upstat job with "start on started hwclock" condition, thus to hint
insserv that upstart can handle starting "hwclock.sh" correctly.
Do I still have to introduce hwclock & hwclock-save init.d scripts as
well? Or does one only need such compat scripts if there are other
sysv init scripts that declare dependency on "hwclock.sh"?
I guess I need to read up on startpar.
Poking around dh_installinit only revealed that correct code to
transition from upstart-job symlink to a normal file is added in the
preinst.
Regards,
Dmitrijs.
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
