Your message dated Tue, 13 May 2014 14:21:41 +0400 with message-id <[email protected]> and subject line Re: Bug#747941: autofs: listing the mount point spams automount -f -v has caused the Debian Bug report #747941, regarding autofs: listing the mount point spams automount -f -v to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 747941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747941 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: autofs Version: 5.0.8-1 Severity: minor Tags: upstream Dear Maintainer, * What led up to the situation? I do not know * What exactly did you do (or not do) that was effective (or ineffective)? I am debugging my automounts and found this error. I hope it's not caused by misconfiguration from my side. When calling automount -f -v, then entering the mount point for autofs, calling 'ls' the console which runs automount -f -v gets spammed * What was the outcome of this action? Spam to automount * What outcome did you expect instead? No output Additional information: output of automount when running 'ls /mnt': (that's where autofs mounts my shares) attempting to mount entry /mnt/tls key "tls" not found in map source(s). failed to mount /mnt/tls attempting to mount entry /mnt/x86_64 key "x86_64" not found in map source(s). failed to mount /mnt/x86_64 attempting to mount entry /mnt/libnss_compat.so.2 key "libnss_compat.so.2" not found in map source(s). failed to mount /mnt/libnss_compat.so.2 attempting to mount entry /mnt/libnsl.so.1 key "libnsl.so.1" not found in map source(s). failed to mount /mnt/libnsl.so.1 attempting to mount entry /mnt/libnss_nis.so.2 key "libnss_nis.so.2" not found in map source(s). failed to mount /mnt/libnss_nis.so.2 attempting to mount entry /mnt/libnss_files.so.2 key "libnss_files.so.2" not found in map source(s). failed to mount /mnt/libnss_files.so.2 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages autofs depends on: ii libc6 2.18-5 ii libxml2 2.9.1+dfsg1-3 ii multiarch-support 2.18-5 ii ucf 3.0028 Versions of packages autofs recommends: ii kmod 16-2 ii module-init-tools 16-2 ii nfs-common 1:1.2.8-6 autofs suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---13.05.2014 12:30, csmo wrote: > Package: autofs > Version: 5.0.8-1 > Severity: minor > Tags: upstream > > Dear Maintainer, > > * What led up to the situation? > I do not know > * What exactly did you do (or not do) that was effective (or > ineffective)? > I am debugging my automounts and found this error. I hope it's not > caused by misconfiguration from my side. > When calling automount -f -v, then entering the mount point for autofs, > calling 'ls' the console which runs automount -f -v gets spammed > * What was the outcome of this action? > Spam to automount > * What outcome did you expect instead? > No output > > Additional information: > > output of automount when running 'ls /mnt': (that's where autofs mounts my > shares) > > attempting to mount entry /mnt/tls > key "tls" not found in map source(s). > failed to mount /mnt/tls > attempting to mount entry /mnt/x86_64 > key "x86_64" not found in map source(s). > failed to mount /mnt/x86_64 > attempting to mount entry /mnt/libnss_compat.so.2 > key "libnss_compat.so.2" not found in map source(s). Wow. Fix your LD_LIBRARY_PATH or /etc/ld.so.conf (or equivalent) setup. Your runtime linker for `ls' tries to find libraries in /mnt, while it should only try that for /lib /usr/lib. Nothing to do with automount really, it is a local configuration error unrelated to autofs. Closing this bugreport. /mjt
--- End Message ---
