CK> Apart from your bug report, we were previously aware of the insserv
CK> issue. I'm still contemplating a solution for this in postinst, but the
CK> problem is that there is no easy way to determine whether the current
CK> runlevels were set by an older cron or by the system administrator. Even
CK> on post-101 installs, the administrator might have manually set (0 1 6)
CK> after the package set (1), so we cannot just delete the links if they
CK> are present.
A debconf item or even file that says "asked them what to do now that we
changed things" perhaps (yuck)?
CK> It is also worth to note that this is merely a cosmetic issue, with
CK> absolutely no side effects (which is why I left it wishlist). If you
CK> want to get rid of the warning, just do
Things shouldn't become different on different machines over time.
CK> # rm -f /etc/rc{0,6}.d/K??cron
Never touch them by hand, Mom says. However, I find, and am reporting
bugs, that both sysv-rc-conf and update-rc.d, have no way, to say "when
I say defaults, I would please like you to use the defaults as found in
the LSB headers for the particular service, and not the hardwired 2345
defaults as found in your program." "Or a new lsb-defaults parameter."
So referring to /var/lib/dpkg/info/cron.postinst I did
# update-rc.d cron remove
# update-rc.d cron start 89 2 3 4 5 . stop 11 1 .
Which makes
# ls -1 /etc/rc?.d/???cron
/etc/rc1.d/K01cron
/etc/rc2.d/S02cron
/etc/rc3.d/S02cron
/etc/rc4.d/S02cron
/etc/rc5.d/S02cron
which I suppose will do.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
