Re: Make use of invoke-rc.d, if available, mandatory?
Lars Wirzenius dijo [Mon, Apr 03, 2006 at 12:38:12AM +0300]:
> Current policy states in section 9.3.3.2 ("Running initscripts") the
> following: "The use of invoke-rc.d to invoke the /etc/init.d/*
> initscripts is strongly recommended[51], instead of calling them
> directly."
> (...)
> I propose that the future has arrived.
Good. Just fixed my packages (haven't uploaded yet, of course, but
will do so).
> (...)
> I would like to see this policy change happen in time for all packages
> to be updated in etch. This would mean that sysadmins can, finally, rely
> on policy-rc.d working reliably. Also it means that it would be easier
> to build chroots, and not have to worry about services and daemons being
> started inside them unnecessarily.
>
> I realize that my script doesn't find all problematic packages. It is
> meant as a quick estimate. For proper testing, I have recently
> implemented changes into piuparts that should make it possible to find
> all problematic packages: in my development version /proc now gets
> mounted (ergo, start-stop-daemon works), and after packages have been
> installed, lsof checks that no processes run inside the chroot. This
> will, I hope, catch packages that don't use invoke-rc.d when they
> should.
My main purpose for this mail is to ensure you there many, many more
packages. Take a look at cherokee, for example - Both its postinst and
prerm had a straight /etc/init.d/cherokee <something>, and it was not
in the list. So, maintainers, beware of your children's misbehaviour.
Greetings
--
Gunnar Wolf - gwolf@gwolf.org - (+52-55)5623-0154 / 1451-2244
PGP key 1024D/8BB527AF 2001-10-23
Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF
Reply to: