http://bugzilla.novell.com/show_bug.cgi?id=567865
http://bugzilla.novell.com/show_bug.cgi?id=567865#c1
Lars Müller changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
Info Provider| |vdboor-fora@codingdomain.co
| |m
--- Comment #1 from Lars Müller 2010-01-04 09:58:57 UTC ---
The INIT INFO part of the smbfs (cifs for post 11.2 systems) ensures the
network get started before and stopped after the smbfs or cifs service.
Please check the order of the symbolic links named /etc/init.d/rc*.d/K*
On a 11.2 system I see for example:
gab:~ # ls -l /etc/init.d/rc5.d/K*{smbfs,network}
lrwxrwxrwx 1 root root 8 4. Jan 10:44 /etc/init.d/rc5.d/K05smbfs -> ../smbfs
lrwxrwxrwx 1 root root 10 11. Nov 20:09 /etc/init.d/rc5.d/K08network ->
./network
or on Factory it's:
giles:~ # ls -l /etc/init.d/rc5.d/K*{cifs,network}
lrwxrwxrwx 1 root root 7 4. Jan 10:52 /etc/init.d/rc5.d/K01cifs -> ../cifs
lrwxrwxrwx 1 root root 10 2. Nov 16:56 /etc/init.d/rc5.d/K08network ->
./network
In both cases the order of the symbolic links is correct.
Please keep in mind that the actual values following the K might be different
on your system as they are calculated dynamically.
I fear that we here face an issue of NetworkManager (NM). NM might get stopped
by the X11 session (KDE or Gnome for example) as the user decided to log off.
@Diederik: Please check the values of the symbolic links. If they fit to the
explanation offered here we have to consult the NM maintainer next.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.