Hi, > What puzzles me, is that you don't have the problem on startup? > After all, network-manager is started in rc2/S20 and nfs already in > rcS/S45mountnfs.sh.
That's right, network-manager starts, takes down eth0 and, an instant later, it comes right up again. It stays on the same network, so it gets assigned the same IP, so the momentary drop is not noticeable except in the logs. > Could you please describe your setup a bit more detailed. If you have > static IPs and no wireless you could consider to switch back to ifupdown > and uninstall network-manager. Sure: No wireless, ethernet with dynamic IP. This box never moves, after all, it would have to leave /home, which is on nfs. I have no need for network-manager at all and uninstalled it right after finding out and filing this bug. The point is, network-manager got installed through gnome-main-menu's Suggests: network-manager-gnome. Everyone who does a fresh install of etch with gnome and uses some kind of networked file system will be haunted by boxes that do not shut down properly anymore (this did not happen on upgrade from sarge). Here's the proposed fix: During installation, ask the user whether they want network-manager to be started or not, providing a friendly warning along the lines of: "If you are using nfs, you should probably say No here. See /usr/share/doc/network-manager/README.Debian for details." Also, please close Bug #415196, it is a duplicate of this one. -- Simon Eilting -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
