[daip] AIPS installation query

[Eric Greisen]

Catherine Brocksopp writes:
 > Final output from install.pl
 > ----------------------------------------------------
 > Password:
 > FILAI1: PASSWORD DOES NOT MATCH --- TRY AGAIN
 > Password:
 > FILAI1: PASSWORD DOES NOT MATCH --- QUITTING

The default password is AMANAGER.  This appears only if it is an
update to a new version (or a 2nd try at the current version) so you
probably do not need to run filaip again.

 > AipsWiz: Here are the final setup instructions for running AIPS
 > 
 >         1.  Reference the LOGIN.SH file in your .profile file
 >               (dot it now too, via ". ./LOGIN.SH")
 
This may be the problem withe the message and Tek servers - see below
fo rdebug info.

 >         2.  Check that it works:
 > 
 >                 aips notv tpok
 > 
 >               (this will not start a TV or tape servers).
 >             Try 'print 2 + 2' for a very basic test.
 > 
 >         3.  Make a cron entry for the do_daily.MSSLN7 file
 >               that the MAKE.MNJ created, so you can run the
 >               AIPS 'midnight job'.  This is optional but
 >               strongly recommended.

    I should fix this - I do not really recommend the MNJ on a cron
(other than perhaps monthly).


 > XAS: ** TrueColor FOUND!!!
 > XAS: ***  Using shared memory option for speed ***
 > XAS: Using screen width height 1430 860, max grey level 255
 > Shared memory id failure: Invalid argument

 > TVSERVER: could not get ssslock service by name: Invalid argument
 > TVSERVER: Check your /etc/services or NIS/YP map
 > ZVTPO3: tcp/aipsmt0 is not a service
 > ZVTPO3: check /etc/services or NIS map!

These 2 issues are addressed on the aips manager FAQ page:

     http://www.aips.nrao.edu/aipsmgr/index.html

You will need to do a bit as root (or with sudo).

To debug the message server issue - try 

1. Copy $SYSUNIX/{UNIX,XAS}SERVERS $SYSLOCAL
2. Edit the 2 files in $SYSLOCAL to uncomment the 2 lines having -hold
   in them

Then the server windows will stay until you manually kill them and any
error messages will remain visible.  The usual error is a
DYLD_LIBRARY_PATH that is not set when the xterm comes up and tries to
run a binary executable.  In general the user's .cshrc, .bashrc, etc
must reference the $AIPS_ROOT/LOGIN.CSH or .SH file even in
non-interactive logins (which the proc-started xterm thinks is the
case).

Eric Greisen