iraf.net

We have a Solaris installation of IRAF and we have a Mac OSX server sharing an nfs mount. This mount is attached to the sun workstation at the root level of the directory structure as /data3. When we try to run some of our data reduction packages on groups of files using wildcard file specifiers nothing happens. I have traced down the problem to what appears to be an iraf bug. Neither the "dir" or the "files" command works properly on the nsf share. If I navigate to a data directory on the nfs share I can list the files using the ls command. If I try to use the dir or dir * command I get a "no files found" response and the "files" command returns nothing. If I enter "dir test.fits" and test.fits exists it will list back test.fits, the same thing happens with the "files" command. The result is that we are able to run out data reduction commands on one file at a time but if we try to process an entire directory nothing happens.We are running version 2.12 for SunOS 4 and Solaris 2.8

Be sure the disk is mounted using the (if I remember correctly) the 'nfsvers=2' option to force the use of NFS v2 protocols. The XServe I believe tries v3 by default and confuses the Suns.Cheers,
-Mike

We are using automount to do the mounting. It is not clear to me how to configure automount to specify a mount version number. If you know how to do this and can provide guidance it would be appreciated.Thanks.

It should just need to be an option you put in the e.g. /etc/auto_<host> file. For instance[code:1:04f2429083]home -rw,intr,soft,nfsvers=2 radix:/home[/code:1:04f2429083]to mount /home from machine 'radix' using v2 NFS. The exact filename will depend on how you've setup your automount files.-Mike

I added the nfsvers=2 line to our auto_direct file. The entry is below/data3 -rw,nfsvers=2 saturn:/data3 I then did a umount /data3 and then ran automount to force it to read the files. I then navigated to /data3 to mount the share. After doing this the mnttab had the following entries for /data3:auto_direct /data3 autofs direct,ignore,dev=3980006 1192214069
saturn:/data3 /data3 nfs rw,nfsvers=2,dev=394004b 1192214076This appears to be correct, but the problem persists.Do you have any other ideas?

It's been a while since I did this: Does the disk show up in the /etc/vfstab as having the nfsvers=2 option? The example I gave may have been linux-specific as it appears the Sun uses an option like "-o vers=2" for the mount_nfs command. You could try manually mounting it with something like[code:1:51d9d4bb20]mount -F nfs -o rw,vers=2 saturn:/data3 /data3[/code:1:51d9d4bb20]Note I'm suggestion vers=2 because of the older SunOS version, it might be that Solaris8 does support vers=3. I don't remember having to do anything special to have the disk exported from the Mac properly. In the end, Google may be more reliable than my memory...-Mike