Date: Wed, 3 Apr 1996 21:54:28 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: deanj@region0.wpafb.af.mil (Dean, Jeffrey D) Cc: questions@FreeBSD.org, schroerj@region0.wpafb.af.mil Subject: Re: NFS Mounts and Symbolic Links? Message-ID: <199604040454.VAA20879@phaeton.artisoft.com> In-Reply-To: <c=US%a=_%p=gov%2Bdms%2Bmilnet%l=ASENT45960403171424BX00190B@asent45.wpafb.af.mil> from "Dean, Jeffrey D" at Apr 3, 96 05:14:23 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> I have created a handy directory with several symbolic links inside it. > After it exporting through NFS, I have come to find out that these symbolic > links are not being shared. Is their a way to correct this without > mount_null'ing these drives (since mount_null'ing is supposed to be > dangerous, and slightly unstable)? -OR- Is their a better way all-around to > do what I'm trying? Symlinks are evaluated by the client kernel (namei in vfs_lookup.c). You will need to maont the file systems containing the link targets on the clinets as well. Since you can't export a file system across a mount point, your "mount_null'ing" idea won't work anyway. If I have the link /home/foo -> /users1/home/foo, then I export the "/home", when a client lookups up "/home/foo", it will get pointed to "/users1/home/foo". Unless you have "/users1" mounted on the client as well, it won't find the link target locally. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199604040454.VAA20879>