https://bugzilla.novell.com/show_bug.cgi?id=665720
https://bugzilla.novell.com/show_bug.cgi?id=665720#c38
Felix Miata
You may try as root
type -p blogd
OK
which should result in /sbin/blogd and with
rpm -qf /sbin/blogd
you should see at least sysvinit-tools.
OK
You may also debug your system by disabling script by script to identify the cause of this random hang (compare with comment #29)
Can you look at comment 37 attachment and suggest which to try or which order to try?
Beside this you may use /var/log/boot.omsg after a reboot to see the former boot/shutdown messages and /var/log/boot.msg to investigate the current boot messages.
Comment 35 attachment provided this, which seems to add little to comment 32.
Clearly you should use the blogd from the attachments of the bug #642289
Are you sure? I am already using that blogd now, but zypper lu shows sysvinit & sysvinit-tools installed are 2.88-37.40.1 while 2.88-37.43.1 are available? Should I install those plus available aaa_base, aaa_base-extras and other available updates before proceeding further? If my comment 25 question was answered, I'm missing it. -- 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.