Package: autofs Version: 4.1.3+4.1.4beta2-3 Followup-For: Bug #130884 The fault is actually pretty harmless - we see it all the time at work, because certain mountpoints are *always* going to be busy (eg, /home), yet restarts still need to be performed (exarcebated currently by a faulty switch that stops letting us talk to random servers at random times). It's pretty harmless, because any new processes will end up using the new mountpoint, and old processes stuck on the old mountpoint will continue to use the old mountpoint. I don't recall whether the last processing exiting from the old mountpoint will automatically unmount the old mountpoint or not -- if not, perhaps the daemon could save the fact that it has registered a USR2, then quit when it can.
Perhaps you are advocating the scenario where the autofs restart script doesn't ask any mounts that are already mounted to be controlled by the new autofs daemon if they fail to be unmounted, to stop there being a duplicate mount. I would caution against this -- you might have asked for new flags or whatever, in which case you want as many processes as possible using the new mount until processes using the stale mount exit. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i586) Kernel: Linux 2.4.26 Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Versions of packages autofs depends on: ii debconf 1.4.46 Debian configuration management sy ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an -- debconf information: * autofs/upgrade-from-broken-version: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
