On Wed, Dec 12, 2012 at 01:54:21PM +0000, Winnie Lacesso wrote:
> Konstantin Olchanski wrote:
> > This disables the super-clever extra-useful network manager feature
> > where it enables networking when a user logs in into the console and
> > helpfully disables the networking when a user logs out from the console.
> 
> Do I grok this aright - you set up an SL workstation to do network stuff 
> in the background, i.e: dhcp renewal, ntp, wee-hours automatic security 
> updates, possibly other things (overnight backups? rsync of data to 
> central server?); but if no one's logged onto the console, those all just 
> stop working bcs NM has shut off the network?
> TUV thinks this is a good idea?! <astonish> 
> 
> It seems badly thought, if someone's not logged on overnight, no security 
> updates. Or does yum rerun its wee-hours cron if someone logs in at the
> console during daytime? 


I do not think this comes from TUV.

It comes from the NetworkManager croud, which I think is the same as
the GNOME croud, or at least they think the same way -
"my laptop^H^H^H^H^H^Htablet is the only use-case that matters".

The normal SL setup (after the installer) is to have "available to all users"
enabled on all system network interfaces and then none of this nonsense happens,
the network functions normally (always enabled).

But I have seen this problem - after the installer, "available to all users" is "off"
and you see the silly behaviour. I discount it as an installer malfunction.


-- 
Konstantin Olchanski
Data Acquisition Systems: The Bytes Must Flow!
Email: olchansk-at-triumf-dot-ca
Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada