https://bugzilla.novell.com/show_bug.cgi?id=487190 Summary: NetworkManager - wrong order of service starts and obviously meaningless service restarts Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: rkrell@gmx.net QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/4.2; Linux) KHTML/4.2.1 (like Gecko) SUSE Recently I checked out NetworkManager instead of the ifup network scripts by installing the appropriate packages and switching it in YaST network configuration, normally as recommended. IMHO, the order of some system services that require a network connection while using NetworkManager is not right (using for instance in runlevel 5). This includes on my system: 1. CIFS file system mounting 2. NFS file system mounting 3. Starting HAL two times: Especially the second start of HAL daemon by the NetworkManager dispatcher during bootup time costs some startup time which might be saved. In this case I'm not sure whether this can be reconfigured, because switching network connections might require HAL to be reloaded. But why does HAL restart completely? Reproducible: Always Steps to Reproduce: 1. Switch to NetworkManager 2. Reboot Actual Results: Boot process: __________________ .. Starting HAL daemon .. Mount CIFS file systems .. Starting NFS client services .. Starting the NetworkManager .. Reload service HAL daemon Shutting down HAL daemon Starting HAL daemon Expected Results: Boot process: __________________ .. Starting the NetworkManager .. Starting HAL daemon .. Mount CIFS file systems .. Starting NFS client services (or something adequate) -- 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.