Path: utzoo!attcan!uunet!seismo!dimacs.rutgers.edu!rutgers!usc!elroy.jpl.nasa.gov!sdd.hp.com!hp-pcd!hpfcso!hpfcdc!rer
From: rer@hpfcdc.HP.COM (Rob Robason)
Newsgroups: comp.sys.hp
Subject: Re: makecdf
Message-ID: <5570529@hpfcdc.HP.COM>
Date: 2 Nov 90 20:22:50 GMT
References: <44@gauss.mmlai.UUCP>
Organization: HP Fort Collins, Co.
Lines: 20

burzio> We have a cluster on our HP machines, allowing the use of CDFs
burzio> on any machine in the cluster.  A file that is cdf'ed may be
burzio> different on each node.  I would like to know from the HP gurus
burzio> if this could be expanded to correctly choose machine names
burzio> across an NFS connection.  This would allow us to store
burzio> binaries, with the same name for different architectures, using
burzio> cdfs.  Right now, you get the file using the NFS servers' name
burzio> (understandable) but it would be better if it was available in
burzio> general.  Comments?

No, CDFs residing on remote systems and accessed via NFS are resolved on
the server.  This means that non-HP servers will not recognize CDFs
(which are just directories with the SUID bit set) as anything other
that normal directories and HP servers will resolve them based on their
own context rather than the client's.  There is nothing in the NFS
protocol that knows about context, so it is impossible to pass context
info to the server for such resolution and still conform to that
protocol.

Rob Robason