Package: sysv-rc
Version: 2.87dsf-4
Severity: minor

Hello,

since 2.87dsf-3 sysv-rc memorizes init-script sequences in
/var/lib/update-rc.d/ and update-rc.d keeps the files there uptodate.
However, update-rc.d does also memorize remove actions in
/var/lib/update-rc.d/, which makes not much sense, IMHO.

Memorizing remove actions leads to dangling files over time. The first
example for this is kbd 1.15-4 which renamed it's conffile
/etc/init.d/console-screen.kbd.sh to /etc/init.d/kbd - which, in turn,
leads to a dangling /var/lib/update-rc.d/console-screen.kbd.sh which
will never get removed from the system automagically.

A cleaner approach here would be to remove the /var/lib/update-rc.d file
along with the last symlink (memorizing the remove before and removing
the memorized information after removing the symlinks sounds nice
somehow :)).

I'm not sure if this is really as easy as it sounds, i.e. if there are
some side-constraints like "there must exist a /var/lib/update-rc.d file
for each /etc/init.d file to make it possible to migrate away from
dependency based boot sequencing" or something like that, but I cannot
imagine a situation where such a constraint would be needed.


Thanks for your work & regards
   Mario
-- 
Do I contradict myself?
Very well, then I contradict myself, I am large, I contain multitudes.
                                                       -- Walt Whitman

Attachment: signature.asc
Description: Digital signature

Reply via email to