Package: autofs Version: 4.1.4-9 Severity: normal autofs(8): "If a map is modified then the change will become effective immediately."
This is not true for NIS-maps. They seems to be cached. Our real-world case is that we are moving home-directories from one NFS-server to another, and changes the NIS-map auto.home accordingly. However, autofs still mounts from the old NFS-server many hours after the change, and hours after unmount of the directory. 'ypcat -k auto.home' looks correct directly after the change, so it seems to be a cache in automount. The mount-point look like this: /usr/sbin/automount --pid-file=/var/run/autofs/_home.pid --timeout=300 /home yp auto_home -rsize=32768,wsize=32768,proto=udp,intr,vers=3 I've seen the problem on several hosts. / Anders -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable'), (1, 'sarge-unsupported') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15.6 Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to sv_SE) Versions of packages autofs depends on: ii libc6 2.3.5-13 GNU C Library: Shared libraries an ii ucf 2.005 Update Configuration File: preserv Versions of packages autofs recommends: ii nfs-common 1:1.0.7-3 NFS support files common to client -- debconf information: * autofs/upgrade-from-broken-version: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
