[CCing debian-init-diversity which is planning to adopt insserv ttbomk] On Tue, 01 Jun 2010 11:15:17 +0800 [email protected] wrote: > Package: sysv-rc > Version: 2.88dsf-7 > Severity: wishlist > File: /usr/share/man/man8/update-rc.d.8.gz > > We read > -f Force removal of symlinks even if /etc/init.d/name still exists. > > However we find that indeed you might as well change that to > > -f [no-op, retained for backwards compatibility] > > or > -f Force removal of symlinks even if /etc/init.d/name still > exists [enabled by default] > > Proof: > > # sysv-rc-conf --list cron > cron 0:off 1:off 2:on 3:on 4:on 5:on 6:off > # update-rc.d cron remove > update-rc.d: using dependency based boot sequencing > # sysv-rc-conf --list cron #GONE: > cron > # update-rc.d cron defaults > update-rc.d: using dependency based boot sequencing > update-rc.d: warning: cron stop runlevel arguments (0 1 6) do not match LSB > Default-Stop values (1)
The -f parameter is mostly just passed along to insserv and causes it to ignore any potential dependency errors afair. If you could remove cron without issues, then this means no other service had a hard dependency on it. At least that's how I understand the meaning of -f. Felipe, is this correct? If so, I guess the correct fix would be to update the documentation of the -f flag accordingly. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pkg-systemd-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
