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

rau

Update AIPS++ sources from the master via ssh.

Synopsis

rau file1 [file2 ...]

Description

rau updates the AIPS++ slave and code areas with the lastest version of a file in $AIPSMSTR. It is provided as an alternative to au which operates on machines on which the AIPS++ master directory is remotely NFS mounted.

In order to use rau 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_keys 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++. rau assumes that you are working within a private directory tree which shadows that of the AIPS++ master source code tree, see mktree (p). The filename arguments specified to rau must be simple filenames without path or RCS ,v suffix. rau determines the corresponding master directory from the current working directory.

rau transmits files from the master host to the local host via ssh as a gzip'd tar file. It gives them a file ownesship defined by the owner of rau (aips2mgr at the local site). rau must itself have the setuid bit set (see chmod). If successful, au then checks out a plain-text copy of the code from the $AIPSRCS subdirectory into the corresponding $AIPSCODE subdirectory. Newly created directories on the master may also be propagated to the local installation.

Programmers on a Linux or Digital UNIX platform, or on any other platform that does not support setuid shell scripts, should instead use a related utility, sau (p). sau runs a non-setuid copy of au, sau.sh, via a C-based setuid wrapper program.

Options

None.

Notes

• rau handles directories as well as files.
• rau is faster than au because
  • 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.

Diagnostics

Status return values
0: initialization succeeded
1: initialization error

Examples

The command

   cd $HOME/aips++/code/install
   rau rau

would update the slave and plain-text copies of rau, but not the script in the AIPS++ bin area.

Bugs

• rau 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 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).
rao (p), invoke ao remotely via ssh(1).
sau (p), AIPS++ code update utility.

Author

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