f8: NetworkManager problem (ex f8: NetworkManager + runlevel 3 problem)
blueser at gmail.com
Wed Nov 14 13:38:53 UTC 2007
On Nov 14, 2007 11:27 AM, Dario Lesca <d.lesca at solinos.it> wrote:
> Il giorno mer, 14/11/2007 alle 11.58 +0100, Dario Lesca ha scritto:
> > Only if I login from vmware console in f8, f8 set IP via DHCP and
> > network work.
> Another problem:
> If I logoff from console all the batch network work (for example run in
> screen) like nfs mount, yum update, ssh connection, ecc there are
> This is not a good thing ...
> Someone have a solution?
> or it's a f8 bug?
> Many thanks
> Dario Lesca <d.lesca at solinos.it>
> fedora-list mailing list
> fedora-list at redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Don't know if this will help, but I've been bitten by a NetworkManager
bug on Ubuntu 7.10 here at work, maybe it also happens on F8:
To sum it all up: disabling "roaming mode" for NetworkManager and
forcing DHCP solved the problem for me (in my case, auotfs failed to
start automatically at boot).
More information about the fedora-list