Bugzilla – Bug 473332
Error in /etc/insserv.conf: "boot.setclock" should be "boot.clock"
Last modified: 2009-02-18 14:38:45 UTC
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8.1.20) Gecko/20081217 Firefox/2.0.0.20 After installing a SuSE 11.0 system, I noticed this: $ chkconfig --del cron cron 0:off 1:off 2:off 3:off 4:off 5:off 6:off $ chkconfig --add cron insserv: Service boot.setclock has to be enabled for service cron insserv: exiting now! /sbin/insserv failed, exit code 1 cron 0:off 1:off 2:off 3:off 4:off 5:off 6:off $ fgrep $time /etc/insserv.conf ^C $ fgrep '$time' /etc/insserv.conf $time boot.setclock +xntpd $ ls /etc/init.d/boot.*clock /etc/init.d/boot.clock* /etc/init.d/boot.getclock* Note that $time in /etc/insserv.conf is defined as 'boot.setclock' but there is no such script /etc/init.d/boot.setclock. I believe $time should be defined as 'boot.clock' rather than 'boot.setclock'... RPM versions: $ rpm -qf /etc/insserv.conf insserv-1.11.0-29 $ rpm -qf /etc/init.d/cron cron-4.1-170 $ rpm -qf /etc/init.d/boot.clock aaa_base-11.0-72 Reproducible: Always Steps to Reproduce: See 'Details'. Actual Results: See 'Details'. Expected Results: "chkconfig --add cron" should not fail. Here is the proposed fix: $ diff -u insserv.conf{.orig,} --- insserv.conf.orig 2009-02-06 09:14:47.000000000 -0600 +++ insserv.conf 2009-02-06 09:14:52.000000000 -0600 @@ -33,7 +33,7 @@ # # The system time has been set correctly # -$time boot.setclock +xntpd +$time boot.clock +xntpd # # Services which need to be interactive
Sorry, now I realize this may be yet another duplicate of: https://bugzilla.novell.com/show_bug.cgi?id=384254 The bug search function didn't find this bug when I searched before. Google did, however... :-)
Archie: If this is a duplicate of bug 384254 , why not marking it as such? Werner, could you please have a look in case this isn't a duplicate? Thank you.
It is a duplicate and yes it is fixed. At least in the latest insserv package for openSuSE 11.0 *** This bug has been marked as a duplicate of bug 384254 ***