On Tue, 2007-08-21 at 13:40 +0200, Tomasz Torcz wrote: > Dnia 16-08-2007, Cz o godzinie 11:52 -0600, Orion Poplawski napisał(a): > > NetworkManager is currently (in devel and F7) unusable with autofs and > > NFS mounts. This is because NetworkManager is stopped very early in the > > shutdown process (K02) and brings down the network with it. Then when > > autofs attempts to unmount any automounted nfs mounts, they fail because > > the remote machine is not accessible. Eventually the machine hangs > > trying to unmount the last nfs mounted directory. I suppose it might > > timeout eventually, but it's beyond my patience to wait that long. > > There is similar NFS issue when switching networks with ~ on NFS. > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=199536 > > Wired IP is released before wireless IP is acquired. This cause a > window of network shortage, which in turn make user's ~ (and gconf > settings) unavailable. > Both problems show NetworkManager problems in IP address management. The problem of NetworkManager is that it does not have _any_ grace period on wired or wirelss disconnections. If you pull the eth0 plug for a few seconds it immediately disables the interfaces and when you plug it in it will acquire a possibly new IP address via dhcp. NM should be more tolerant of disconnections, not remove the IP immediately and try to reset previous values if the wired interface comes back in a very short period of time (I say up to 60sec. at least). It is very annoying to loose all connections when all it happened is someone removed a patch for a few second from the patch panel while working on it. Simo. -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
