John Andersen wrote:
On Monday 01 December 2003 16:34, Sid Boyce wrote:
That's a possibility, but the sort of failures are things like cups, apache2 and ssh which are pretty much standalone. I haven't seen anything in the scripts that seem out of the ordinary. Regards Sid.
--
No, they all need network to be up before they start. So look carefully at your services sequence in /etc/rc.d and see if network is starting too late. You can often see this problem is your network is pcmcia and is not started immediatly. Sometimes you have to fiddle with the sequence a bit, and thats where you edit the script for failing services and make sure all the depends on lines are correct. Then man insserv.
It doesn't look that way from what I see in /var/log/boot.msg, I also don't get these failure with the SuSE kernel. I suspect hotplug for some of it as on previous2.6.0-pre kernels, I had to get rid of it to get it to boot minus my usb stuff. <notice>start services (network) Setting up network interfaces: lo done eth0 IP/Netmask: 192.168.10.1 / 255.255.255.0 done <notice>exit status of (network) is (0) <notice>start services (syslog) ###<Stuff deleted> ### <notice>exit status of (syslog) is (0) <notice>start services (hotplug) Starting hotplugging services [ ieee1394 net pci usb ............................ ]failed <notice>exit status of (hotplug) is (1) <notice>start services (resmgr) ### A LONG WAY DOWN ### Starting SSH daemonfailed Starting INET services. (xinetd)failed Master Resource Control: runlevel 5 has been reached Failed services in runlevel 5: hotplug sshd rsyncd mysql lpd xinetd nscd Skipped services in runlevel 5: smbfs nfs acpid splash Regards Sid. -- Sid Boyce .... Linux Only Shop.