archive get [getopts] file1 [file2 ...]
archive mv* [mvopts] file1 [file2 ...] target
archive rm* [rmopts] file1 [file2 ...]
archive ls [lsopts] [file1 ...]
archive stat [statopts] [name]
archive mkdir [mkdiropts] dir1 [dir2 ...]
archive rmdir* [rmdiropts] dir1 [dir2 ...]
archive chmod* [chmodopts] mode file1 [file2 ...]
archive chgrp* [chgrpopts] group file1 [file2 ...]
archive chown* [chownopts] owner[:group] [file1 ...]
archive migrate* -(M|u|q) [migrateopts] file1 file2 ...]
* The current version of archive does not support the commands
indicated with asterisks (*). Later versions will incorporate
these additional commands.
Copy files file1 [file2 ...] from the current working directory to the archival storage system. Options putopts include -retry N, -asf host, -C path, -s, -f, -i, -p, -M, -D, -n, -t tarfile, -S, and -z. file1 [file2 ...] may contain wildcards * and ?.
The destination directory on the archival storage system may be specified using the -C path option. If -C path is not present, the user's archival home directory will be used.
Multiple files are combined with tar(1) before copying to the archival storage system if the -t tarfile option is specified. Files are tarred by first executing
tar cf - run10 run10.001, ..., run10.025 > tarfile
then tarfile is transferred to the archival storage system.
Copy files file1 [file2 ...] in the archival storage system to the current working directory. Options getopts include -retry N, -asf host, -C path, -s, -f, -i, -p, -M, -n, -S, -x, and -z. If wildcards * and ? are used in specifying file1 [file2 ...], then double quotes must be used:
archive get "file1 [file2 ...]"
A source directory on the archival storage system may be specified using the -C path option. If -C path is not specified, the user's archival home directory will be used.
Archival storage files with a .tar, .tar.gz, or .tgz extension will be extracted with the gzip and tar utilities if the -x option is present. For example, if filea is named run10.tgz, then archive get -x will copy run10.tgz from the archival storage system, then execute
gunzip -f < run10.tgz | tar xf -
Specifying -x has no effect on files with extensions different
from .tar, .tar.gz, or .tgz.
Move file1 [file2 ...] to the target location target; file1 [file2 ...] and target are all located on the archival storage system. Options mvopts include -retry N, -asf host, -C path, -s, -f, -i, -M, and -n. If target is an existing directory, then file1 [file2 ...] are moved into target. If target does not exist, archive mv will attempt to rename file1 as target. If in this case [file2 ...] is present or the names file1 and target are identical, archive mv will fail and write an error message to standard error. If wildcards * and ? are used to specify file1 [file2 ...] and target, then double quotes must be used:
archive mv "file1 [file2 ...]`` ''target"
Note: do not include both file1 [file2 ...] and target in the
same set of quotes. If wildcards are used to specify file1
[file2 ...] or target, but not both, then quotes need only
delineate the argument containing wildcards.
Remove file1 [file2 ...] on the archival storage system. Options rmopts include -retry N, -asf host, -C path, -s, -f, -i, -r, and -n. If wildcards * and ? are used to specify file1 [file2 ...], then double quotes must be used:
archive rm "file1 [file2 ...]"
When -r is specified, directories are emptied of files and removed.
The user is prompted for removal of any write-protected files, except
when the -f option is used.
List [file1 ...] on the archival storage system. Options lsopts include -retry N, -asf host, and other options identified by the manual page for ls on the archival storage system. (See man archive_ls(3) for a full list of lsopts.) If wildcards * and ? are used to specify [file1 ...], then double quotes must be used:
archive ls "[file1 ...]"
If [file1 ...] is not specified, then the contents of the user's home
directory on the archival storage system are listed.
Check and report status of archival storage system. Options statopts include -retry N, -asf host, and -s. An exit status of 0 is returned when the system is operational; a non-zero exit status is returned otherwise. A message of the form
hh:mm:ss mm/dd/yyyy name status [note]
is printed to standard out, where hh:mm:ss mm/dd/yyyy is the current
date, name is the name of the archival storage system, status is
either ``on-line'' or ``unavailable'', and note is an optional text
message that may or may not be returned.
Create directories dir1 [dir2 ...] on the archival storage
system. Options mkdiropts include -retry N, -asf host,
-C path, -s, -p, -m mode, and -n.
Remove empty directories dir1 [dir2 ...] from the archival storage system. Options rmdiropts include -retry N, -asf host, -C path, -s, -p, and -n. If dir1 [dir2 ...] are not empty, archive rmdir will fail and print an error message to standard error. If wildcards * and ? are used to specify dir1 [dir2 ...], then double quotes must be used:
archive rmdir "dir1 [dir2 ...]"
Change permissions for file1 [file2 ...] according to mode.
Options chmodopts include -retry N, -asf host,
-C path, -s, -R, and -n. mode may be either symbolic
or absolute. See discussion of mode syntax in the OPTIONS section
under -m mode.
Change the group ID of file1 [file2 ...] to group, which
may be a decimal group ID or a group name found in the group file.
Options chgrpopts include -retry N, -asf host, -C path,
-s, -f, -h, -R, and -n. Only an appropriately authorized
user may change the group of a file that is owned by another user.
Unless users are appropriately authorized, they must be a member of the
specified group to change the group of a file. Unless the user is
appropriately authorized, archive chgrp clears the set-user-ID and
set-group-ID file mode bits.
Change the owner of file1 [file2 ...] to owner; The
optional group argument changes the group. Options chownopts
include -retry N, -asf host, -C path, -s, -f,
-h, -R, and -n. Only an appropriately authorized user may
change the owner of a file. Unless the user is appropriately authorized,
archive chown clears the set-user-ID and set-group-ID file mode
bits.
Control file migration of file1 [file2 ...]; Options migrateopts include -retry N, -asf host, -C path, -s, -n, -M, -u, and -q. Options -M, -u, and -q specify the operation performed by archive migrate, and only one may be given in a command. -M migrates a remote file or set of files. -u unmigrates a remote file or set of files, and -q prints a message indicating whether or not the file(s) are migrated. If none of these three options are given, -M is assumed.
* archive currently does not support the options identified below with
asterisks (*). There are two acceptions: -f is assumed, but sufficient
error checking to enforce -f for all possible errors is not currently
enabled. Also, -m mode currently only handles asolute (as
opposed to sybmolic) mode specification. Later versions of archive will
include all of the options and behavior listed below.
File modes may be either symbolic or absolute. Absolute changes to modes are specified with octal numbers, with mode of the form nnn. Here n is a number from 0 to 7.
An absolute mode is given as an octal number constructed from the ``OR'' of the following modes:
Symbolic changes to modes are specified with mnemonic characters, with mode of the form
[who] operator [permissions]
Note: if who is specified, there should be no space between who and operator; similarly, if permissions is specified, there should be no space between operator and permissions. Here who is one or more characters that corresponds to user, group, other, or all (u, g, o, or a); operator is +, -, or =, signifying the addition, removal, or absolute assignment of permissions; and permissions is one or more characters that correspond to the type of permission, e.g., read (r), write (w), execution (x) for a given file. For example, to add read and write permission for group, mode should be g+rw.
Multiple symbolic modes separated by commas can be specified, although no spaces may intervene between these modes. Operations are performed in the order given. Multiple symbolic letters following a single operator cause the corresponding operations to be performed simultaneously.
By default mode is 777 (a+rwx) minus the bits set in the umask on the archival storage system.
archive mkdir -p dir1/dir2To get a listing of all files that end with .tex in directory d1 on the data archive:
archive ls "d1/*.tex"To put local files f1 and f2 into a zipped tarfile files.tgz into directory dir1 on the mass store and delete the local copies:
archive put -C dir1 -D -z -t files.tar f1 f2To tar a local directory localdir into and put the tar file (tarfile.tar) in remote directory remotedir:
archive put -C remotedir -t tarfile.tar localdirTo get and extract files from tarfile files.tar in mass-store directory dir1, and save (not delete) the tarfile in the local directory:
archive get -C dir1 -x -S files.tarTo get a file from directory dir1 and make sure that the remote file is still/again migrated to slow storage:
archive get -C dir1 -M file
Each environment variable is a comma-separated list (with no white
space), representing multiple archival storage facilities. Currenlty
all archive commands operate on only one system and use the first
element of each list, which is interpretted by archive as the
default. A different system may be specified with the -asf option.
In the future, archive get, stat, and ls will be modified to
operate on multiple systems, sequencing through the entries in the
lists for these environment variables.
Centers currently supported include ERDC, NAVO, ASC, AHPCRC.
archive_get(3),
archive_mv(3)*,
archive_rm(3)*,
archive_ls(3),
archive_stat(3),
archive_mkdir(3),
archive_rmdir(3)*,
archive_chmod(3)*,
archive_chgrp(3)*,
archive_chown(3)*.