> >
> > > >
> > > > Have to mention that there is a NIS map which refers to a direct mount
> > > > for some SUN clients.
> > > autofs does not support direct mounts. Check out Alvin�s autofs HOWTO
> > >
> > > http://www.Linux-Consulting.com/Amd_AutoFS/autofs-HOWTO.html
> > >
> >
> > What I would like to know, dows autofs ignore safely this map entry so
> > that we can use the same maps for all hosts, or may it become
> > confounded, so that we need at least a special auto.master for Linux
> > hosts ?
> >
>
> It should just ignore it.
>
It still does not do this:
jnix@scheat:~ > mount
/dev/sda3 on / type ext2 (rw)
proc on /proc type proc (rw)
/dev/sda7 on /var type ext2 (rw)
/dev/sda9 on /usr type ext2 (rw)
/dev/sda10 on /opt type ext2 (rw)
/dev/sda11 on /mnt/data1 type ext2 (rw,bsdgroups)
/dev/sda2 on /boot type ext2 (rw)
/dev/sda8 on /var/tmp type ext2 (rw)
helios:/mnt/linuxlocal on /usr/local type nfs (rw,nosuid,addr=xxx.xxx.111.55)
automount(pid174) on /home type autofs (rw,fd=6,pgrp=174,minproto=2,maxproto=3)
automount(pid193) on /vol type autofs (rw,fd=6,pgrp=193,minproto=2,maxproto=3)
automount(pid204) on /data type autofs (rw,fd=6,pgrp=204,minproto=2,maxproto=3)
-> automount(pid223) on /- type autofs (rw,fd=6,pgrp=223,minproto=2,maxproto=3)
garp:/u on /vol/unix type nfs (rw,nosuid,hard,intr,bg,addr=xxx.xxx.111.15)
jnix@scheat:~ > ps aux p223
USER PID %CPU %MEM SIZE RSS TTY STAT START TIME COMMAND
root 223 0.0 0.2 1064 636 ? S 12:13 0:00 automount -t 300 /- y
p /etc/auto.direct hard,intr,nosuid,bg
Besides, we still have the problem that NFS mounts using autofs stop
to work sometimes. That means that something like /vol/unix above
disappears after some time (after a week), or not shows up directly
after booting. But the entry in the mount tables seems to stay, this
means if I shut down autofs, "mount" still tells me that /vol/unix is
mounted. It looks like "autofs" died. I can only fix this by a reboot.
This happens with 2.0.36 kernel on two machines, and with 2.2.5 kernel
on another machine. Distribution is SuSE 6.0 and SuSE6.1.
If we use NFS and mount static via fstab, we have no problem.(But we
can not use this for mounting homes).
Also, the problem has been observed with local filesystems.
We have the following entry in auto.vol, which is meant to be used by
Sun machines. For Linux the directory does not exist. Could this cause
the occasional failure?
openwin -suid,ro kirk:/ext1/${OSNAME}${OSREL}-openwin
tim:/fuji/openwin-v3.sunos41x
Can a error condition with DNS or NIS (e.g. DNS server down or NIS
server not responding for some short time) induce such an error?
Johannes
