Hi Kyle,
symbolic links are never followed on the NFS server, they must be
processed on the client.
This is part of the NFSv{2,3,4} protocol specification.
You should check why nfsv3 client is able to mount those NFS filesystems
to which the symlinks
are pointing to. And why nfsv4 client cannot mount them. Check the snoop
output.
--Pavel
Kyle McDonald wrote:
> I know it may not be the best idea to do this, but in order to shorten
> the length of pathnames in DHCP options I ended up making soflinks to
> directories much lower in the filesystem.
>
> With NFSv3, if the client had permission to mount the direcotry the link
> pointed at, everything was good. Now with NFSv4 as the default, all
> those clients are getting denied access.
>
> Is there some easy way to get the NFSv4 server to follow them?
>
> I know I can selectively, or globally force shares from this server to
> only be vers=3, but I think I'd rather just enable the old behavior if
> possible.
>
> -Kyle
>
> _______________________________________________
> nfs-discuss mailing list
> nfs-discuss at opensolaris.org
>
