If for some reason /etc/init.d/clock would fail, syslog and cron can and should still start, because the kernel knows what time it is anyway. At least here it does (kernel 2.6.10) -- I found this out while printing $(date +%H:%M:%S.%N) after the "[ ok ]" message, the kernel knows the correct time right from the start when the scripts mount proc. So I decided that I don't need the clock script (as I have no need for --adjust and --systohc either), brought it down with '/etc/init.d/clock stop', and was amazed to see it brought syslog and klog and cron down with it. Stopping the clock service does not unset the system clock, so there is no need to stop the log and cron services. And although it could be argued that these services should refuse to start if the system time hasn't been set successfully, I would prefer them to run with a wrong clock than not to run at all. So those services should 'use clock' and not 'need clock'. Reproducible: Always Steps to Reproduce: 1. 2. 3.
file a bug each offending package ive fixed the baselayout-specific scripts (bootmisc), but the other scripts you've mentioned have nothing to do with baselayout
> ive fixed the baselayout-specific scripts (bootmisc) But you didn't remove clock from the CRITICAL_SERVICES in /sbin/rc, so it would still start if it were rc-update delled. (BTW, hadn't this CRITICAL_SERVICES variable better be defined somewhere in /etc/conf.d instead of in a script that gets overwritten every so often?) > file a bug each offending package Ehm, how to do that then? Choose component 'Unspecified' and then put the package name in the Summary line? I don't see an explanation on how to file a package-specific bug. (And come on, Mike, you probably know who's responsible for sysklogd and vixie-cron and could forward them the bugnumber in a jiffie.)
that, unfortantely, is not a quick fix *** This bug has been marked as a duplicate of 70009 ***
