https://bugzilla.novell.com/show_bug.cgi?id=384254
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384254#c74
--- Comment #74 from Dr. Werner Fink 2008-05-26 03:13:05 MDT ---
If /etc/init.d/boot.clock or /etc/init.d/boot.setclock is missed then the
bug is driver by the same behaviour of insserv: by default it does not
igmore errors anymore. The current insserv from factory tries to determine
if the script used for execution (the parent) is executed by rpm it ignores
know errors (hopefully temorary errors). Next is that aaa_base from factory
now uses /etc/init.d/boot.clock again, no /etc/init.d/boot.setclock, but
/etc/init.d/boot.getclock. This should avoid that during an update there
exists temporary two scripts providing both boot.clock in the LSB header.
Nevertheless if the error once happened it can only be repaired with
a) updating both insserv and aaa_base from factory *and*
b) executing the command line
insserv boot.clock
by hand. This because the rpm post install script assumes that if the
start link for boot.clock is missed the user had removed this link and
therefore no new link is required.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.