https://bugzilla.novell.com/show_bug.cgi?id=426270
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=426270#c43
Dr. Werner Fink changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
Info Provider| |psankar@novell.com
--- Comment #43 from Dr. Werner Fink 2008-12-12 03:24:54 MST ---
This what it should be. The question is: *Why* boot.clock is disabled
even if all other scripts have been enabled by the installation script
of the package aaa_base. To see the scripts provided by the package
aaa_base you may run
rpm -ql aaa_base | grep /etc/init.d
the README, rc, boot, skeleton, and are skeleton.compat specials whereas
the scripts mentioned in comment #38 are enabled by default in a fresh
installation and in the update case only if the link is already enabled.
This you may check by using
rpm -q --scripts aaa_base | less +/boot.clock
therefore the question is ... as already mentioned ... why boot.clock
is disabled as the only exception?
Please do a
cd /var/log
find YaST2/ zypp/ zypper.* -type f | xargs zgrep boot.clock
this takes a few minutes but if there was an error during installation
it should be detected.
Beside this I'd like to see the files /etc/insserv.conf, the output of
rpm -V aaa_base insserv
rpm -qi aaa_base insserv
also I'd like to know if you're using some custom packages and/or
packages from any other contribution, e.g. from any repository of
opensuse.org. This lead my to the next question, What does the
command line
rpm -qa --triggers --scripts | grep -B3 -A14 boot.clock
show ... note that the last command takes several minutes. Nevertheless
if there is any package on your system which interfere with aaa_base
we should see this if there is more than one match.
--
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.