hi Matt,
So, just to be clear: are you saying that you want to present your users
with an NFS resource something like:
codeserver:/project/
code
data
where "code" resides on codeserver, but "data" resides on another NFS
server, e.g on dataserver?
If so, then there is something we are working on that would provide a
solution: NFSv4 Referrals.
When a client system accessed the "data" path, codeserver would return a
"MOVED" error to the client, and also refer the client to the real
location of the data, namely to dataserver.
We don't yet have a firm schedule for delivering this work, but it is
under discussion.
A quick workaround would be for you to use e.g. symlinks to
/net/dataserver under your "data" area, but you probably considered that
already.
Otherwise, as you've noted, it's not possible for Solaris to re-share,
or proxy, NFS services from another server.
hope this helps.
cheers,
calum.
> Security is not a concern.
>
> I have access to place code onto ServerB but not on the NFS Server.
> The clients that are accessing the NFS share need the code on ServerB
> and files on the NFS server. So In order to co-locate the code and
> files I would like to re-share from ServerB to any number of clients.
>
>
> It is not a matter of the clients not being allowed access to the NFS
> server. It's a matter of having control over on box and not another.
