Getting Started

Documentation

Glish

Learn More

Programming

Contact Us

Version 1.9 Build 1556

News	FAQ
Search	Home

AIPS++ accounts and groups

A set of AIPS++ accounts and groups have been defined to perform particular functions. The following descriptions include the standard names, user ids, and group ids, but different names may be defined via the aipsrc (p) mechanism:

• aips2adm (uid=31414, gid=31414): Owns the master AIPS++ directories, RCS version files and ftp distribution files. aips2adm is responsible for maintaining the ftp directories, and in particular, runs the exhale (p) cron job on the master host aips2.nrao.edu. aips2adm's other functions are described in chapter 13. This account usually need only be created in Socorro.

• aips2mgr (uid=31415, gid=31415): Owns an AIPS++ installation, including directories, source files and binaries. At development sites, aips2mgr, and those in the aips2mgr group, are RCS and ftp administrators for an AIPS++ installation. In particular, they can directly invoke the rcs command on the AIPS++ RCS files. aips2mgr has an active login account but this may be restricted to selected machines. aips2mgr runs the daily inhale (p) cron job.

• aips2prg (uid=31416, gid=31416): A generic programmer account and group. In practice the account may not often be used but the aips2prg group lists those who have permission to check sources into AIPS++, or check them out with a write lock (see §9); there are no restrictions on checking sources out without a write lock.

• aips2usr (uid=31417, gid=31417): The aips2usr account is intended to serve as a generic AIPS++ usage account. The aips2usr group could be used to control access to AIPS++ executables and AIPS++ data areas if this degree of control was desired by the AIPS++ manager (the alternative being to give world execute and/or write permission). Neither the account nor the group are currently recognized by the system.