Getting Started

Documentation

Glish

Learn More

Programming

Contact Us

Version 1.9 Build 1556

News	FAQ
Search	Home

Subsections

• Synopsis
• Description
• Options
• Notes
• Diagnostics
• Examples
• Bugs
• See also
• Author

ae

Extricate an AIPS++ source file from a half-completed checkin/out.

Synopsis

ae file

Description

ae extricates a source file in the current directory from a half-completed RCS checkin/out. Such problems sometimes arise when the checkin/out is interrupted part way through leaving behind an RCS semaphore file.

The presence of a defunct RCS semaphore file is indicated by repeated ``in use'' errors when a checkin or checkout of a file is attempted.

ae assumes that you are working within a private directory tree which shadows that of the AIPS++ master source code tree, see mktree (p). It determines the corresponding master directory from the current working directory.

The filename argument must be a simple filename without path or RCS ,v suffix.

ae invokes $MSTRETCD/ae_master, where $AIPSMSTR is expected to be NFS mounted from the AIPS++ master host (see §1.1.4). It waits till the semaphore file is at least 15 minutes old before deleting it in case a slow RCS transaction is in progress.

Options

None.

Notes

• The semaphore file has a name of the form ,file, and resides in the same directory as the master RCS version file (file,v).

• The utility which generates updates for the AIPS++ code distribution system exhale (p) routinely searches for and deletes all semaphore files which are more than a day old. ae allows particular semaphore files to be deleted on a much shorter timescale.

• ae uses an AIPS++ utility called tract (p) to determine the age of the RCS semaphore file.

Diagnostics

Status return values
0: success
1: initialization error
2: semaphore file not found
3: failed to delete semaphore file

Examples

The command

   cd ~/aips++/code/aips/implement/FooBar
   ae Foo.cc

would delete the RCS semaphore file for Foo.cc if it existed.

Bugs

• ae requires that the host operating system support setuid shell scripts. Some operating systems, most notably Linux and Digital UNIX, do not support setuid shell scripts for security reasons.

See also

The manual page for ci(1), the RCS checkin command.
AIPS++ variable names (§1.2).
AIPS++ code management configuration (§1.1.4).
ai (p) AIPS++ code checkin utility.
ao (p) AIPS++ code checkout utility.
mktree (p) create AIPS++ directory hierarchy.
tract (p) report the age of a file or directory.

Author

Original: 1995/02/23 by Mark Calabretta, ATNF.