On 05/31/2010 03:00 PM, [email protected] wrote:
> CK> So the LSB headers in /etc/init.d/cron say that (1) is the default
> CK> level, but your /etc/rc?.d directories contain symlinks for (0 1 6).
>
> # Default-Start: 2 3 4 5
> # Default-Stop: 1
> $ /usr/sbin/sysv-rc-conf --list cron
> cron 0:off 1:off 2:on 3:on 4:on 5:on 6:off
>
> CK> These symlinks probably came from an older cron installation (pre-101),
> CK> is it possible that you've been using (+upgrading) that system since then?
>
> All I know is that I've used Debian since 2000, 2005, and 2009 on my
> three computers.
That's probably the cause then.
> How could /etc/init.d/cron never be updated during apt-get upgrade?
For valid reasons, -101 removed levels 0 and 6 from the default
runlevels. This only affected new installations, existing symlinks were
not touched to preserve possible local changes.
See update-rc.d(8), section "INSTALLING INIT SCRIPT LINKS" for a rationale.
> Or shouldn't changes like this be presented to the user with a dialog
> asking what to do, "accept the maintainers change, or keep my own
> version, etc.?"
Not for runlevel symlinks.
> Somebody, not me, blew it, by not keeping components up to date?!?
See above.
Apart from your bug report, we were previously aware of the insserv
issue. I'm still contemplating a solution for this in postinst, but the
problem is that there is no easy way to determine whether the current
runlevels were set by an older cron or by the system administrator. Even
on post-101 installs, the administrator might have manually set (0 1 6)
after the package set (1), so we cannot just delete the links if they
are present.
It is also worth to note that this is merely a cosmetic issue, with
absolutely no side effects (which is why I left it wishlist). If you
want to get rid of the warning, just do
# rm -f /etc/rc{0,6}.d/K??cron
on the affected systems.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
