On Fri, 2007-11-09 at 08:13 -0700, Charles Curley wrote: > On Fri, Nov 09, 2007 at 04:24:06PM +0530, Rahul Sundaram wrote: > > Dario Lesca wrote: > >> In F8 on a PC-A I have start NetworkManager + > NetworkManagerDispatcher. > >>> From another pc (PC-B), via ssh connection, i switch PC-A from > runlever > >> 5 to 3 via "init 3" > >> Network is stop. my shell on PC-B stop work! > >> grrrr! then I goto on console of PC-A and "service network restart" > >> come back to my PC-B, my shell now work! > >> do some work (in runlevel 3) > >> then re-switch PC-A (via ssh from PC-B) to runlevel 5 via "init 5" > >> Network is stop. my shell on PC-B stop work! > >> grrrr! Is this a correct behavior? Is NM incompatible with runlevel > 3 ? > >> Thanks to all for your reply!! > > Here's the problem: NetworkManager (NM) and the network "service" are > incompatible. If NM is running, it will obliterate the setup the > network service, so running "service network restart" gets you only > temporary relief. > > Also, going from run level 5 to 3 shuts down NM's gnome applet. In the > process of shutting down, it tells NM to shut down all network > connections. > > What I recommend you do is shut down MN entirely, and prevent it from > running. Use system-config-services to do this. Make sure the network > service is enabled. > > Then use system-config-network (while in run level 5) to configure > your network. Your network configuration should now survive run level > changes (except, of course, to 6). > > If you have a laptop, keep NM on the system, and run it only when you > are away from home. That is what I have done. NM works with wired connections and wireles connections. I use it wherever I am and it works very well. -- ======================================================================= "He don't know me vewy well, DO he?" -- Bugs Bunny ======================================================================= Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@xxxxxxxxxxxxx
