[daip] aips help

[Eric Greisen]

Jonah White writes:
 > We are using Linux and we did a binary install.  This is what the commands
 > give:
 > 
 > whitejp at HYDRA [/project/twj-vol4/pete/soft/AIPS] % source LOGIN.CSH
 > whitejp at HYDRA [/project/twj-vol4/pete/soft/AIPS] % $CDTST
 > AIPS_VERSION=/project/twj-vol4/pete/soft/AIPS/31DEC07
 > whitejp at HYDRA [/project/twj-vol4/pete/soft/AIPS] % cd DA00
 > Directory: /project/twj-vol4/pete/soft/AIPS/DA00
 > whitejp at HYDRA [/project/twj-vol4/pete/soft/AIPS/DA00] % ls -laF
 > total 24
 > drwxrwsr-x 5 whitejp jonestw  121 2007-06-15 13:45 ./
 > drwxrwxr-x 9 whitejp jonestw 4096 2007-06-18 10:30 ../
 > drwxrwsr-x 2 whitejp jonestw   18 2007-06-18 10:33 COMA/
 > -rwxrwxr-x 1 whitejp jonestw 1738 2007-06-18 10:30 DADEVS.LIST*
 > drwxrwsr-x 2 whitejp jonestw   18 2007-06-15 14:04 HYDRA/
 > -rwxrwxr-x 1 whitejp jonestw 2910 2007-06-18 10:30 NETSP*
 > -rwxrwxr-x 1 whitejp jonestw 2508 2007-06-18 10:21 PRDEVS.LIST*
 > -rwxrwxr-x 1 whitejp jonestw   35 2007-06-15 13:45 TPDEVS.LIST*
 > -rwxrwxr-x 1 whitejp jonestw 1884 2007-06-18 10:30 TPHOSTS*
 > drwxrwsr-x 2 whitejp jonestw    6 2007-06-15 13:45 VIRGO/

 > whitejp at HYDRA [/project/twj-vol4/pete/soft/AIPS/DA00] % cd $HOST
 > Directory: /project/twj-vol4/pete/soft/AIPS/DA00/HYDRA
 > whitejp at HYDRA [/project/twj-vol4/pete/soft/AIPS/DA00/HYDRA] % ls -laF
 > total 0
 > drwxrwsr-x 2 whitejp jonestw  18 2007-06-15 14:04 ./
 > drwxrwsr-x 5 whitejp jonestw 121 2007-06-15 13:45 ../
 > -rwxrwxr-x 1 whitejp jonestw   0 2007-06-15 14:04 SPACE*
 > 

Boy - this is baffling.  File creation seems just to hang - there
should be a whole bunch of files in DA00/$HOST.  You could try copying
$TST/$ARCH/TEMPLATE/* to DA00/$HOST.  Make sure that you have rw
privilege on them all.  Then try
            RUN FILAIP
again.  There should be a bunch of error messages about files already
exist and then it should create a few more files.

One question - are you running the daemons that allow your file system
to do file locking: the aipsmgr FAQ says

 Error message from ZLOCK claiming "no locks available"
     File locking requires the certain daemon processes (services)
     be running in the operating system.  Which processes these are
     depends on the OS.  Linux RedHat 7.2 systems seem to require
     lockd, statd, and nfsd.  More modern Linux distributions have
     services turned off unless the installer explicitly turns them
     on.  These systems need nfs and nfslock services.  Enter
          /etc/init.d/nfs status
          /etc/init.d/nfslock status
     to see if they are running.  The rpc.statd is often the rpc that
     has been overlooked.

If they are not running there may be a problem locking SPACE which is
needed to create files.  If the lock code hangs rather than returning
the "no locks available" error, then you could get what you have seen
so far.

Eric Greisen