https://bugzilla.novell.com/show_bug.cgi?id=348318
User delgado@dfn-cert.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c13
--- Comment #13 from Friedrich Delgado Friedrichs 2008-05-14 07:03:54 MST ---
It seems we get a wrong order of links in the runlevel directories, each time
one of the init scripts in the early range is touched.
A correct order on our machines is:
S05network
S06syslog
S07auditd
S07dbus
Network has to start before syslog, because we use remote logging. dbus has to
start after syslog, because it tries to send messages to syslog when starting
up. We also use non-parallel init for several reasons.
This time the /etc/init.d/network script was changed after the sysconfig update
yesterday. Strangely this led to dbus trying to start even before the network.
This can be fixed by calling insserv -d
After the installation of sysconfig I get the following error:
Preparing... ########################################### [100%]
1:sysconfig ########################################### [100%]
/etc/sysconfig/network /
./SuSEfirewall2: FW_DEV_EXT: any -->
/
insserv: There is a loop between service network and haldaemon
Updating etc/sysconfig/network/dhcp...
Updating etc/sysconfig/network/config...
Removing old autogenerated device configuration files:
either network should not require hal, or dbus should not use syslog, as this
makes remote logging impossible.
It is impossible to get rid of dbus and hal altogether, since they seem to be
required by lots of packages, some of which are integral parts of the system.
Whats the reason for network requiring hal?
Maybe I'm missing an obvious solution here.
--
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.