1756630 Members
2723 Online
108849 Solutions
New Discussion юеВ

Re: Correct use of NFS

 
Joseph Huber_1
Honored Contributor

Re: Correct use of NFS

But then the solution is easy:

the clients mount command needs once and for all fix the mount path (or the logical name resulting in) to say "/export/dir".
There is to my knowledge no way around specifying a subdirectory: in Unix speech "/export" is a device path only, and TCPIP mount "speaks" Unix in this regard.

Then only the server side need to change when the disk/directory becomes different:

Map /export to the new disk.
Create a directory alias (or hardlink on ODS5 disks) [DIR] pointing to the new directory,
then "/export/dir" need not be changed at all, and all the clients can mount without changing a single character in the pathname.
http://www.mpp.mpg.de/~huber
Wim Van den Wyngaert
Honored Contributor

Re: Correct use of NFS

Ok J but I avoid hardlinks. I was searching for a pure tcpip thing (e.g. via mapping).

Wim
Wim
Jan van den Ende
Honored Contributor

Re: Correct use of NFS

Wim,

if I understand correctly, you want to be able to just use:

SOMEDIR:

as a directory spec?

In that case you CAN
$ DEFINE/SYSTEM/EXEC SOMEDIR DNFS:[topdir.subdir]
Then you just
We have been using it for some time (although it has been quite some time ago).

Proost.

Have one on me.

jpe
Don't rust yours pelled jacker to fine doll missed aches.