autofs {3, 4, 5} and bind mounts which point to other automount points
The ability to have automount point to automount is something I use heavily as well. Otherwise I end up with many hundreds of nfs mounts on the server at a time. having hundreds of bind mounts on the client is preferrable. The old sun method of doing this was:
host:/path/name:dir
which would mount host:/path/name and then symlink dir. Now we' d use bind/loopback mounts. But that syntax has been gone a long time.
It doesn't seem like threading should inherently cause a problem. Each request should be a new thread and wait for the underlying mount (which might be recursive) to finish.
Ian Kent
maintainerQuoted 6 lines · Joe Pruett
The ability to have automount point to automount is something I use heavily as well. Otherwise I end up with many hundreds of nfs mounts on the server at a time. having hundreds of bind mounts on the client is preferrable. The old sun method of doing this was:
host:/path/name:dir
which would mount host:/path/name and then symlink dir. Now we' d use bind/loopback mounts. But that syntax has been gone a long time.It doesn't seem like threading should inherently cause a problem. Each request should be a new thread and wait for the underlying mount (which might be recursive) to finish.
It does cause a problem.
The process group is used by the kernel module to prevent the daemon itself from triggering mounts. In the threaded environment there is currently one program group so one thread cannot cause another thread to trigger a mount.
I'll have to fix it.
Ian