[daip] AIPS TV device

Eric Greisen egreisen at nrao.edu
Mon Dec 1 12:29:31 EST 2003


Miguel de Val Borro writes:

 > We have replicated the AIPS installation in a read-only AFS
 > volume. For the $ARCH/MEMORY area we have created another
 > volume writable by the users. Is it safe to have it accesible
 > from all users' workstations? What can be a reasonable quota? 10MB?

     Quota?  The ME file in the $ARCH/MEMORY needs to be writable but
its size will not increase.

 > 
 > I've been testing to have the writable areas DA00 and
 > DATA/SAERIMNER_1 accesible from workstations with different
 > architecture but there are problems. Now we have AIPS installed
 > in Solaris and Linux, should the writeable areas be independent
 > in both installations? Is it possible to have a common data
 > area?

Here we have

$AIPS_ROOT/DA00/<host_name>/

where <host_name> are link files to a writable area on the actual host
(and <host_name> is in caps e.g. PRIMATE.  Architectures are fully
mixed here although in HOSTS.LIST the solaric machines are in one
"site" and the Linux ones in another.  The data areas are also all
mounted through pointer files to real disks on the workstations.  We
do something fancier but

$AIPS_ROOT/DATA/<host_name_n>/ 

would work.  Then the DADEVS.LIST file may simply list these link
files.

You must keep the data areas for different architectures separate.  It
is possible for a solaris machine to destroy a user's data files that
were created by Linux and vice versa.  That is why we use separate
site names for the two byte orders.

Eric Greisen



More information about the Daip mailing list