Getting Started

Documentation

Glish

Learn More

Programming

Contact Us

Version 1.9 Build 1556

News	FAQ
Search	Home

Subsections

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

amv

AIPS++ file and directory renaming utility.

Synopsis

amv [ -src | -top ] old new

Description

amv is used to rename AIPS++ files and directories. It does not do any renaming itself but instead appends renaming commands to the action list contained within ax_master (p). It then invokes ax_master on the master AIPS++ RCS repository which must be available (see §1.1.4). The renames will be applied to the slave RCS repositories and system by inhale (p) and sneeze (p) respectively. This mechanism allows AIPS++ slave sites to follow changes made to the master.

General users can rename directories at or below the third level below $AIPSCODE (see §1.1.1). In particular, this includes module and application subdirectories. Renaming of higher-level directories is only allowed for members of the aips2mgr group.

Options

-src

Rename files or directories in the AIPS++ RCS repository and code subtree. Both arguments must be specified as a pathname relative to $AIPSCODE (and therefore $AIPSLAVE and $AIPSMSTR. For example,

   amv -src aips/implement/Foo.cc vlbi/implement/Bar.cc

would result in the following renames:

   $AIPSMSTR/aips/implement/Foo.cc,v -> $AIPSMSTR/vlbi/implement/Bar.cc,v
   $AIPSLAVE/aips/implement/Foo.cc,v -> $AIPSLAVE/vlbi/implement/Bar.cc,v
   $AIPSCODE/aips/implement/Foo.cc   -> $AIPSCODE/vlbi/implement/Bar.cc

the first when ax_master (p) is invoked by amv itself, and the other two when invoked by inhale (p). The following deletions will also result when ax_master is invoked by sneeze (p):

   $AIPSARCH/lib/libaips.a(Foo.o)
   $AIPSARCH/libdbg/libaips.a(Foo.o)

-top

Rename a file or directory beneath $AIPSROOT. Both arguments must be specified as a pathname relative to $AIPSROOT. For example,

   amv -top docs/README docs/ReadMe

would result in renaming

   $AIPSROOT/docs/README  -> $AIPSROOT/docs/ReadMe

when sneeze (p) invokes ax_master (p). Note the following:

   amv -top master/old master/new
   amv -top slave/old slave/new
   amv -top rcs/old rcs/new

The first only renames the master RCS version file, the second only renames the slave RCS version file, and by convention the third renames both.

Resources

• account.manager: Account name and group of the owner of the AIPS++ source code. amv only allows members of the aips2mgr group to delete higher-level directories. $HOME/.aipsrc is ignored.

Notes

• amv uses av (p) to verify new filenames and creates addenda to the av filename cache for them.

• It is an error for the new name to refer to a file or directory which already exists - use ax (p) to delete any such pre-existing file or directory if necessary.

• It is not permitted to rename a file or directory in the AIPS++ system areas. This must be done by using the -sys option to ax (p) to delete the file or directory and relying on a system rebuild to recreate any missing files.

• When ax_master (p) is invoked on the master RCS repositories it uses a temporary action list placed in MSTRETCD/ax_list by amv. This mechanism prevents the same renames being applied by ax_master twice in the same version of AIPS++.

• Renames may be disabled by creating a file $MSTRETCD/amv_disable. If this file contains any text it will be printed as an informative message.

• amv must be setuid to aips2mgr.

Diagnostics

Status return values
0: success
1: initialization error
2: usage error
3: failed to get ax_master

Examples

To move a module subdirectory from the trial package (see §1.1.1) to the aips package use

   amv -src trial/implement/Module aips/implement/Module

It may be convenient in csh and some other shells which allow it to use a command of the form

   amv -src aips/implement\{,/FooMan}/Chu.cc

The shell would expand this to

   amv -src aips/implement/Chu.cc aips/implement/FooMan/Chu.cc

Refer also to the examples provided in the ``Options'' section above.

Bugs

• amv 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

AIPS++ code management configuration (§1.1.4).
AIPS++ variable names (§1.2).
inhale (p), AIPS++ code import utility.
sneeze (p), AIPS++ system rebuild utility.
av (p), AIPS++ filename validation utility.
ax (p), AIPS++ code deletion utility.

Author

Original: 1993/07/23 by Mark Calabretta, ATNF.