[daip] a TV display problem on a linux machine

[Eric Greisen]

Min S. Yun writes:

 > We installed the 31DEC01 version of aips on Cutthroat today
 > with minimum difficulty.  It replaced the 15DEC99 version.
 > When we fired up AIPS for the first time, however, the exactly the same
 > problem with TV happened again -- if we issue 2 TVINITs, the
 > second one hangs the TV.  We did INET installation for TV,
 > so we tried "aips tv=local" and our TV problem seemed to have
 > disapppeared!!  So, there is something wrong with our INET
 > setup?

       I have no idea!  This problem occurred one other place and was
never tracked down - at least you have a work around.  The sys admin
suggested that there might be an Xauthority problem but I would not
know what that would mean.

 > 
 > One other thing we are trying to do is to have use Cutthroat
 > as the main aips host and try to run aips on other Lynux boxes
 > by cross-mounting the disks.  Not surprisingly, this was not
 > a smooth process.  Our system manager person insisted on this
 > path because he did not want to install aips on all our machines.

      We agree with him and have only 1 AIPS for the whole AOC (Now).
It supports 3 architectures (SGI, Solaris, Linux).  To get the codes -
we put all of aips below /home/AIPS which all computers mount.  The
HOSTS.LIST lists all hosts, setting the $ARCH which then lets the
right load modules etc be selected.

     We - our sys-admin - use the automounter with a file we call
auto.DATA which maps a "key" (e.g. PRIMATE_1) to a real location (e.g.
primate:/export/home/primate/AIPS/DA01).  The Yellow Pages NIS make
file has to include this file.  Then anyone in the building can cd
/DATA/PRIMATE_1.  The DA00 files in $AIPS_ROOT/DA00/<host> are then
just pointers (ln -s) to real data areas on the actual computer- e.g.
primate:/export/home/primate/AIPS/DA00.  The DADEVS files occur in
DADEVS.LIST and DADEVS.LIST.COAOARN for the LInux machines all of
which are given "site" COAOARN while the SGI and Solaris are NRAOAOC.


 > He, along with Chris and I, managed to muddle thru some of
 > this stuff, but we just don't understand what "ZLOCK: No locks available"
 > means.  For example, trying to run aips on Rainbow using aips
 > located on a cross-mounted disk on Cutthroat, 
 > 
 > TVDEVS.SH: Starting TPMON daemons on RAINBOW asynchronously...
 > ZLOCK: No locks available
 > ZLOCK: No locks available
 >  ZMSGER: ON FILE DA01:MSD001000.001;                             
 >  ZMSGER: IN ZDAOPN ERRNO = 37 (No locks available)
 > ZLOCK: No locks available
 >  ZMSGER: ON FILE DA01:MSD001000.001;                             
 >  ZMSGER: IN ZDAOPN ERRNO = 37 (No locks available)
 >  ZDCHIN: COULD NOT READ PARAMETER FILE
 >  ZDCHIN: (USING MINIMUM SYSTEM CONFIGURATION)
 > Begin the one true AIPS number 1 (release of 31DEC01) at priority =   0 
 > ZLOCK: No locks available
 > ZLOCK: No locks available
 >  ZMSGER: ON FILE DA01:MSD001000.001;                             
 >  ZMSGER: IN ZDAOPN ERRNO = 37 (No locks available)

    Our sys-admin suspects that you are not running the lock daemon
process lockd.  If you are running it, then he will need to know
details of your system - where is it from, version, kernel version,
etc.

 > I suspect there is a right procedure for doing this.  If there is
 > a procedure for this type of installation, please point
 > us to it.  Many thanks for all your help.

We have not written up a proc for doing this since it gets in bed with
profession sys-admins and they all know the "right" way to do it -
they just do not agree.  We have a working one here that seems to have
resolved gotcha over the years. although we just overhauled it some in
the last months.

I hope some of this helps...

Eric