On Wed, 2008-06-11 at 17:55 +0200, Max Harvest wrote: > On Wed, Jun 11, 2008 at 4:09 PM, Jeff Moyer <[EMAIL PROTECTED]> wrote: > > "Max Harvest" <[EMAIL PROTECTED]> writes: > > > >> Hello everybody, > >> > >> since i'm using the automount 5, i'm confronted with a very strange > >> behaviour. I use it to mount user directories over nfs. The automounter > > > > Are you saying that you did not experience this problem with autofs v4? > > > > yes. I have downgraded to version 4 and everything works fine, but > this is not very satisfactory. > > >> maps are provided by NIS und users ususally have to login only into > >> client computers remotely using rsh or ssh. Now i encounter the following > >> missbehaviour: > >> > >> At the init, automounter seems to start propperly, but if someone logins > >> over the network into the client machine, the automounter ignores all > >> mount requests (i.e. there is no automounter activity at all). Even a > > > > This is probably because there is no lookup performed (meaning it never > > gets to autofs). What errors are displayed in the ssh session when a > > user logs in? Is there anything in /var/log/secure or /var/log/messages > > that may indicate a problem elsewhere? > > of course there are lookups. But if an ssh or rsh login occurs, the message > is 'no such file or directory'. There is no message from automount in syslog > (only from ssh, that confirms a login). It happens exactly as i wrote, a > login through tty lets automount read the indirect maps and from this point > automunt also reacts to lookups on remote logins. The strange thing is, that > reading the indirect map happens without any lookup, just a login on tty > (e.g. root login). I'm just curious which event cause the secoud part of the > output i posted earlier.
This description and the information you provided is not sufficient to work out what's going on. Do this on a test machine: Ensure autofs debug logging is enabled. With autofs stopped (obviously you need to log into an account that doesn't use automounted directories). Check that no automount related mounts are active by inspecting /proc/mounts. Start autofs. Attempt to log in from a remote machine using an account that does use an automounted directory. Attempt to log in locally using an account that does use an automounted directory. Log both sessions out. Stop autofs. Post resulting log here. Ian _______________________________________________ autofs mailing list autofs@linux.kernel.org http://linux.kernel.org/mailman/listinfo/autofs
