[daip] AIPS TV device

[Eric Greisen]

Miguel de Val Borro writes:
 > Now it works adding a number after 'tv=local:'. The problem was that
 > there was a daemon left that didn't allow to open the TV server 1.
 > 
 >   PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
 >  5910 rolandk    9   0   892  892   704 S     0.0  0.0   0:00 TPMON1
 > 

    TPMON1 has nothing to do with the TV, TEK etc servers

 > Now it is possible to run the TV server with numbers up to
 > tv=local:9 , for higher numbers AIPS try to run the TV server
 > number 2 which is already taken.
 > 
 > $./aips tv=local:10

    The numbers are in extended hex 0-9,A-Z not 10

 > 
 > START_AIPS: Starting TV servers on saerimner asynchronously
 > START_AIPS:  - WITH Unix Sockets as requested...
 > START_AIPS: Starting TPMON daemons on SAERIMNER asynchronously...
 > Starting up 31DEC03 AIPS with normal priority
 > Begin the one true AIPS number 1 (release of 31DEC03) at priority =   0 
 > AIPS 1: You are not on a local TV device, welcome stranger
 > AIPS 1: You are assigned TV device/server   2
 > AIPS 1: You are assigned graphics device/server   2
 > AIPS 1: Enter user ID number
 > ?UNIXSERVERS: Start TV LOCK daemon TVSRV1 on saerimner
 > TVSERVER: Starting AIPS TV locking, Unix (local) domain
 > UNIXSERVERS: Start XAS1 on saerimner, DISPLAY localhost:10.0
 > XAS: ** TrueColor FOUND!!! 
 > XAS: Using screen width height 1142 800, max grey level 255
 > XAS: Cannot use shared memory on remote XAS link
 > XAS: !!! Shared memory not selected !!!
 > MakeLink: bind error (UNIX): Address already in use

   When a socket has been used and closed, the system takes some time
to discover this fact - actually as much as 5 minutes in some cases.
The socket number may not be reused in the interval.  This is the
typical message that appears in that case although typically it is
with Inet sockets.

How many windows servers are you running simultaneously off one
server?

Eric Greisen