Getting Started | Documentation | Glish | Learn More | Programming | Contact Us |
Version 1.9 Build 1556 |
|
AIPS++ hosts database.
$AIPSROOT/aipshosts
The aipshosts database is an ASCII file containing a list of AIPS++ hosts at a site (or possibly at a set of sites within an institution). It is used by the aipsinit (p) scripts in defining the $AIPSPATH environment variable.
aipshosts provides a means of specifying an architecture and site for a set of AIPS++ hosts. Its existence was prompted by the fact that there is no generic way to determine a machine's architecture. However, in addition to machine architectures, the architecture may differentiate between operating system versions or compilers where there is a choice of these at a particular site. Hosts from several sites within an institution may be included within one aipshosts file thereby making it possible to copy an AIPS++ installation verbatim from the central site to a remote site.
aipshosts is initially constructed by the configure (p) script when AIPS++ is first installed. Thereafter it can be maintained manually by adding, deleting or modifying entries as required.
Each host has a one-line entry in the aipshosts file, the format of which is as follows:
The host ``architecture'' is a string of the form <base>[_<ext>]. The base part of the name describes the binary format of a machine and reflects the combination of machine architecture and operating system. Because some AIPS++ scripts may need to switch on architecture type, the base part of the architecture name has been standardized. Currently recognized values are:
alpha ...DEC/Alpha, OSF/1 hpux ...Hewlett-Packard, HPUX ibmrs ...IBM RS6000, AIX sgi ...Silicon Graphics, IRIX sun4 ...SUNsparc, SunOS 4.x sun4sol ...SUNsparc, Solaris 2.x
An optional extension to the architecture type can be used to select between alternative systems of the same binary format, for example as may have been generated by different compilers, or different compiler options. Apart from not containing an ``_'' or ``:'', the extension may be freely chosen. However, in order to provide template makedefs (p) and aipsrc (p) files when AIPS++ is installed, configure (p)) recognizes a number of standard combinations. Specifically
Where it's desired to maintain several systems using different compiler options within the one AIPS++ installation (for example, different levels of optimization) this may be denoted by On, where n is an optional digit. This should be placed after any compiler specification, separated by a "-", for example, sun4sol_gnu-O2. (Note that AIPS++ already supports separate debug and optimized compilations within each system.)
Any architecture extension defined in aipshosts serves only as the default for a particular machine. aipsinit (p) provides a mechanism which allows it to be redefined on demand.
Comments within the aipshosts file are denoted by a # in column 1, and blank lines are ignored.
Note that when hosts are added to the system the host-specific system area may be created beneath $AIPSSITE (§1.2) to hold host-specific databases (see aipsrc (p)). Likewise, when a host is removed its system area should be deleted.
The following might be a fragment of an aipshosts file covering all of ATNF.
# AIPS++ host database DEFAULT sun4sol_ntv epping cetus sun4sol_ntv epping Sun Ultra 1, AIPS++ server Room 85 raptor sgi_gnu epping Silicon Graphics, computer room. corvus sun4sol_gnu culgoora Sun 4/65 SPARC 1+, control room. yeti alpha_gnu parkes AlphaServer 1000 4/266
AIPS++ variable names (§1.2).
aipsinit (p), AIPS++ initialization procedure.
aipsrc (p), AIPS++ resource database.
configure (p), AIPS++ installation script.
makedefs (p), AIPS++ makefile definitions.