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
• See also
• Author

rao

Check out AIPS++ sources by invoking ao (p) remotely via ssh.

Synopsis

rao [

options for

ao]

Description

rao is an ssh-based front-end to ao (p). It checks out files by running ao on the AIPS++ master host and transmitting them to the local host via ssh as a gzip'd tar file. This is provided as an alternative to invoking ao directly on a machine on which the AIPS++ master directory is remotely NFS mounted. In order to use rao a programmer must have an account on aips2.nrao.edu and it must be set up for ssh access from the local host via a suitable entry in the .ssh/authorized_keys file (.ssh/authorized_keys2 for ssh2). The programmer must also have an up-to-date AIPS++ workspace on aips2.nrao.edu and it must be rooted at $HOME/aips++ (see mktree (p)). Visit the Using SSH page for more details on using ssh in AIPS++.

Options

Refer to the options for ao (p). rao itself has no options.

Notes

• rao handles directories as well as files.
• rao is faster than ao because
  • It only has to do one file transfer rather than two.
  • It transfers files in compressed form.
  • The overhead involved in the invokation of ssh is much less than that of one automount of a remote filesystem.
• When accessing aips2.nrao.edu via ssh the programmer's login initialization scripts (e.g. .bashrc, .cshrc, .esrc, .login, .profile, .rcrc, .tcshrc) must not consume stdin or write to stdout or stderr.
• Where the account name on the aips2.nrao.edu differs from the local account name an environment variable may be used to translate between them:

     AUID="<remotename>"
  

  The .ssh/authorized_keys file (.ssh/authorized_keys2 for ssh2) for the remotename account on aips2.nrao.edu should have an entry for each machine you may want to use remotely.

  you will need to run ssh-keygen and put the generated key in the .ssh/authorized_keys on aips2.nrao.edu

• ssh is used as the transfer agent rather than ftp since the latter requires a password to be supplied for each remote access.

• rao will prompt the user if writable copies of the files being checked out exist, allowing the user to choose between replacing them and aborting the check-out. Each file will be prompted for separately.

• rao will print a warning message when it removes locally-unwritable (read-only) copies of files in order to replace them with the checked-out copies.

Diagnostics

Status return values
0: success (returned from ao_master)
1: initialization error, no checkout

Examples

The command

   rao -l Foo.cc

would check out Foo.cc with an exclusive lock. Then

   rao -u Foo.cc

would remove the lock without checking the file in or deleting the working copy. The command

   rao -l RCS/*,v

would check out everything in the directory (that is, assuming that RCS is a symlink into the slave directory, all files currently in the slave directory will be checked out of the master).

See also

The manual page for co(1), the RCS checkout command.
The GNU manual page for gzip(1).
The unix manual page for ftp(1).
The unix manual page for ping(1).
The unix manual page for ssh(1).
ai (p), AIPS++ code checkin utility.
ao (p), AIPS++ code checkout utility.
au (p), AIPS++ code update utility.
mktree (p) create AIPS++ directory hierarchy.
rai (p), invoke ai remotely via ssh(1).
rau (p), update AIPS++ sources from the master via ssh(1).

Author

Original: 1996/08/06 by Mark Calabretta, ATNF.