[lsb-discuss] [PATCH] LSB install_initd / remove_initd exit codes are undefined

Tobias Burnus tobias.burnus at physik.fu-berlin.de
Sat Jun 21 03:54:22 PDT 2003


I just realized that currenty the behaviour of /usr/lib/lsb/install_initd
and /usr/lib/lsb/removed_initd is undefined if no the dependencies are not
fulfilled or will be broken, respectively.

The attached patch adds these rules:

a) install_initd
   (i)   successful installation: exit 0
   (ii)  already installed:       exit 0
   (iii) missing required boot facility: exit 1
   (iv)  other errors (cannot access init script database etc.):
         undefined/ignored by this patch (an exit status != 0 is useful!)

b) remove_initd
   (i)   successfully removed: exit 0
   (ii)  not installed:        exit 0
   (iii) other init script depends on this one: exit 1 and not removed
   (iv)  other problems: not defined/ignored by this patch
         (an exit status != 0 is useful in this case!)

Especially the wording of the remove_initd paragraph is a bit clumsy. If
you find better word, go ahead!

The described behaviour is implemented that way in
SuSE 8.2/UnitedLinux 1.0 and with restrictions in Debian.
(Debian gives these exit status codes but it will install/remove a package

Don't forget to run "make" in lsb/spec/wip/sysinit/ after applying this

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: installinit.sgml.diff
Url: http://lists.linux-foundation.org/pipermail/lsb-discuss/attachments/20030621/30e2f91b/attachment.txt 

More information about the lsb-discuss mailing list