[daip] Issue with the AIPS tv on the CENTOS 7

Eric Greisen egreisen at nrao.edu
Mon May 7 11:29:23 EDT 2018


On 05/06/2018 11:52 PM, ABINASH KUMAR SHAW wrote:
> Hi Eric,
> 
> Thank you for your reply. I have tried the alternative way by adding the 
> suggested commands to the .Xdefaults in my user profile. I have also 
> tried the first method but could not understood what to do with the  
> HOSTS.LIST and the data areas.
> 
> Is there any way or any flag which I can change before starting the 
> installation which corresponds to a server installation of the software 
> and take care of all the things  automatically?

There really isn't a way to do everything automatically.  Screen 5 of 
install.pl says

Site type",
  "\n****** READ CAREFULLY - HAS CHANGED ******\n\n" .
  "If your site consists of a single computer, especially\n " .
  "if it may get different names at different times,\n " .
  "it is best to force the name for AIPS to LOCALHOST.\n ",
  "If you do not want this, enter N or n [Y]");

I assume you responded with a y or simple carriage return.  Had you said 
N or n, then install.pl would have used your actual host name and build
the various files with it.  But adding a second host does not happen
automatically in any case.

Here at NRAO we have a great many AIPS computers.  They all use the same 
single AIPS installation located on a file server that services all 
local Linux computers.  Your e-mails do not make it clear that you have 
a similar setup for your 2 machines.  I will send snippets from the 
various files we have here:

In $AIPS_ROOT there are the 2 files LOGIN.CSH and LOGIN.SH.  They both 
say LAPTOP="NO" rather than YES.

Also in $AIPS_ROOT, there is HOSTS.LIST a snippet of which looks like

+  PECOS      LNX64   COAOARN  NONE   Pentium 400 MHz, John Benson
+  PHECDA     LNX64   COAOARN  NONE   Dual Xeon 1.8GHz, Public Linux
+  PILABO     LNX64   COAOARN  NONE   Dual Quadcore 2.66GHz Xeon, fowen
+  POLIS      LNX64   COAOARN  NONE   Precision Tower 3620, kradford
+  PRIMATE    LNX64   COAOARN  NONE   Pentium 500 MHz, Eric Greisen
+  PYANFAR    LNX64   COAOARN  NONE   Pentium 4 3GHz, Jean Eilek 32-BIT

Note + in column 1, 2 spaces. host name, host architecture, site name, 
NONE, and a comment.  After the host name it is free format.

In the $AIPS_ROOT/DA00 area there are directories pointing at each host 
to contain the control files for that host.  You probably have a 
directory call LOCALHOST which is - at the moment used by both machines.

They contain files made by FILAIP and look like

/home/AIPS/DA00/PRIMATE
primate<132>$ ls
ACD000000;  BAD001009;  BAD002009;  MED000005;  SPD000000;  TPD001007;
BAD001001;  BAD002001;  BQD000000;  MED000006;  TCD000001;  TPD001008;
BAD001002;  BAD002002;  GRD000000;  MED000007;  TDD000004;  TPD001009;
BAD001003;  BAD002003;  ICD000000;  MED000008;  TPD001001;  TPD00100A;
BAD001004;  BAD002004;  MADFFFFFF;  MED000009;  TPD001002;
BAD001005;  BAD002005;  MED000001;  MED00000A;  TPD001003;
BAD001006;  BAD002006;  MED000002;  MED00000B;  TPD001004;
BAD001007;  BAD002007;  MED000003;  PWD000000;  TPD001005;
BAD001008;  BAD002008;  MED000004;  SPACE       TPD001006;

If your host name is HOST1 then

cd $AIPS_ROOT/DA00

ln -s LOCALHOST HOST1

will let you use that area for host1.  For host 2

mkdir HOST2
cp HOST1/* HOST2/

will make up the 2nd machines area

The file $AIPS_ROOT/DA00/DADEVS.LIST contains the names of the data 
areas.  These names MUST contain the name of the host so that the start 
up script will know which files to include - a snippet from ours looks like

-  /DATA/PLANETS_1
-  /DATA/PLANETS_2
-  /DATA/PLANETS_3
-  /DATA/POLIS_1
-  /DATA/PRIMATE_1
-  /DATA/PRIMATE_2
-  /DATA/PRIMATE_3
-  /DATA/PRIMATE_4
-  /DATA/PRIMATE_5

Note the - in column 1, 2 blanks, then the path to the data area.

I hope this helps.

Eric Greisen




More information about the Daip mailing list