On Thu, 2 Jun 2005, Michael Marion wrote:
> I just noticed an improper behavior with 4.1.4 (and patches) regarding /net
> that I've not seen yet.
>
> I just upgraded a host to 4.1.4 with the latest patches from kernel.org:
> autofs-4.1.4-misc-fixes.patch
> autofs-4.1.4-multi-parse-fix.patch
> autofs-4.1.4-non-replicated-ping.patch
>
> /net is mounting the paths improperly if there's only one export from a host..
>
> i.e.
> kydland SOURCES {504}$ /etc/auto.net cornholio
> -fstype=nfs,hard,intr,nodev,nosuid \
> /local/mnt cornholio:/local/mnt
> kydland SOURCES {505}$ ls /net/cornholio
> suse-9.2 workspace x86_64
> kydland SOURCES {506}$ mount | grep cornholio
> cornholio:/local/mnt on /net/cornholio type nfs
> (rw,nosuid,nodev,hard,intr,addr=129.46.234.38)
>
>
> vs:
> kydland SOURCES {507}$ /etc/auto.net uranium
> -fstype=nfs,hard,intr,nodev,nosuid \
> /local/mnt uranium:/local/mnt \
> /local/scratch uranium:/local/scratch
> kydland SOURCES {508}$ ls /net/uranium
> local
> kydland SOURCES {509}$ mount | grep uranium
> uranium:/local/mnt on /net/uranium/local/mnt type nfs
> (rw,nosuid,nodev,hard,intr,addr=129.46.26.26)
> uranium:/local/scratch on /net/uranium/local/scratch type nfs
> (rw,nosuid,nodev,hard,intr,addr=129.46.26.26)
I'll check this out.
>
> I'm still using a program map for /net.. had issues with mounts to something
> where as soon as one path failed to mount, the rest were ignored. I remember
> someone mentioning an option to automount that would fix that, but when I
> tried it (a long time ago) it didn't work, at least not for me.
The default has changed.
This should be OK.
Ian
_______________________________________________
autofs mailing list
[email protected]
http://linux.kernel.org/mailman/listinfo/autofs
