Package: connman Version: 0.10+git20090203t223225-0ubuntu1 Severity: important Tags: patch User: [email protected] Usertags: missing-dependency
With dependency based boot sequencing, I discovered what I believe is a bug in the init.d script. The script is missing the dependency information required for dependency based boot sequencing, and would get the default header. I notice the update-rc.d call only insert start symlinks in runlevels 2-5, and replicate this in the header. I find it strange that this service should not stop in runlevel 1, and ask you to consider if the Default-Stop header should list runlevel 1 (and the update-rc.d call in the postinst changed to reflect this as well as adding code to reinsert the script with a symlink in runlevel 1). I notice the script start rather late in the boot sequence, but find no information about why. If there are other scripts it should start after, those should be listed in the dependency header as well. <URL: http://refspecs.freestandards.org/LSB_2.1.0/LSB-generic/LSB-generic/initscrcomconv.html > documents the LSB header format. Some debian notes are available from <URL: http://wiki.debian.org/LSBInitScripts >. This patch should solve the issue. Without it, the script will stop in runlevels 0, 1 and 6, and perhaps start to early in the boot sequence. diff -ur connman-0.30+git.1.5b69740e1+dfsg/scripts/connman.in connman-0.30+git.1.5b69740e1+dfsg-pere/scripts/connman.in --- connman-0.30+git.1.5b69740e1+dfsg/scripts/connman.in 2009-07-22 10:35:35.000000000 +0200 +++ connman-0.30+git.1.5b69740e1+dfsg-pere/scripts/connman.in 2009-08-27 10:25:54.461204000 +0200 @@ -1,4 +1,13 @@ #!/bin/sh +### BEGIN INIT INFO +# Provides: connman +# Required-Start: $network $remote_fs $syslog +# Required-Stop: $network $remote_fs $syslog +# Default-Start: 2 3 4 5 +# Default-Stop: +# Short-Description: Connection Manager +### END INIT INFO + daem...@prefix@/sbin/connmand DESC="Connection Manager" Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
