Getting Started

Documentation

Glish

Learn More

Programming

Contact Us

Version 1.9 Build 1556

News	FAQ
Search	Home

Subsections

• Synopsis
• Description
• See also
• Author

.profile

AIPS++ .profile file.

Synopsis

. .profile

Description

The .profile file which resides in $AIPSROOT is installed there as part of the AIPS++ system to provide a minimal environment for Bourne-like shells (sh, ksh, bash) for the AIPS++ manager.

In particular, .profile is used to define the environment for the AIPS++ manager's cron jobs, and also for .rshexec (p).

If inhale (p)) is being run to keep the AIPS++ installation in step with the master then any changes made to this file would be overwritten whenever the system master was modified. Additional definitions or redefinitions may instead be made in a separate .profile_local file which is invoked by .profile as its last operation before invoking aipsinit.sh (p).

If .profile_local is present it must define the PATH and MANPATH environment variables, but must not invoke aipsinit (p). If .profile_local is not present .profile will supply reasonable but probably inadequate defaults for PATH and MANPATH.

The commands contained in .profile are executed upon login (or if the shell is invoked via a name beginning with "-"). They usually consist of terminal setup commands and environment variable definitions which are automatically inherited by every subprocess.

Remote shells such as are activated by rsh do not read the .profile file (assuming that sh, ksh or bash is the default login shell). In such cases the .rshexec (p) command should be used.

The Bourne-shell startup files are read in the following order:

   .profile
   .profile_local

See also

The unix manual page for cron(1).
AIPS++ variable names (§1.2).
aipsinit (p), AIPS++ initialization procedure.
.cshrc (p), aips2mgr's .cshrc file.
.login (p), aips2mgr's .login file.
.rshexec (p), AIPS++ remote execution utility.

Author

Original: 1992/04/30 by Mark Calabretta, ATNF.