upclient(8dfs)

Synopsis

upclient -server machine -path {filename | directory_name}... [-time frequency]
[-file log_file] [-verbose] [-help]

Options

-server machine
Specifies the DCE pathname of the machine (for example, /.../abc.com/hosts/fs1) whose files are to be periodically checked. The machine should be either the System Control machine for the cell or domain or the Binary Distribution machine for the local machine's CPU/operating system type.

-path {filename | directory_name}
Names each file or directory to be checked periodically on the local disk of the machine specified with the -server option. If multiple paths are supplied, they must be unique, disjoint trees in the file system. Paths are examined from left to right; paths that intersect with previous paths used in the command are logged as errors (if a log file is specified with the -log option) and ignored.

If you specify a directory, the upclient process recursively checks all files and directories located beneath the specified directory. Therefore, you can specify a / (slash) to check all files and directories on the local disk of the machine specified with the -server option.

-time frequency
Specifies in number of seconds how often the upclient process is to check each file or directory specified with the -path option. The default is 300 seconds (5 minutes).

-file log_file
Names the log file on the local machine to which errors are to be written. Because multiple upclient processes can be run on one machine, choose a distinct filename for the log. If this option is omitted, no errors are logged.

-verbose
Directs the upclient process to produce detailed information about its actions each time it checks for new versions of files (as specified with the -time option). The process lists each file and directory object it checks and any changes it makes to local versions of these objects. The output is sent to standard error.

-help
Prints the online help for this command. All other options specified with this option are ignored.

The help and apropos commands available with all command suites are also available with the upclient command. See the bos help and bos apropos reference pages for examples of using these commands.

Description
The upclient command initializes the client portion (upclient process) of the Update Server. The upclient process periodically checks specified files and directories on the local disk of the server machine specified with the -server option to be sure they match the corresponding files and directories on the local machine (the machine running the upclient process). If a file on the specified server machine does not match the version on the local machine, the upclient process requests the newer version from the server portion (upserver process) of the Update Server on the specified machine. It then overwrites the local version of the file with the newer version.

The upclient process is usually started and controlled by the BOS Server; if it is not, execute the upclient process as a background process. The binary file for the upclient process resides in dcelocal/bin/upclient.

The -time option specifies how often the upclient process is to check for changed versions of files and directories. The -path option specifies the files and directories the upclient process is to check. If you specify a directory, the upclient process recursively checks all files and directories located beneath the specified directory. To check all files and directories on the indicated server machine, specify a / (slash) with the -path option.

If you specify multiple files and directories with the -path option, the paths must be disjoint (nonintersecting). Path names specified with the -path option are examined from left to right. Any path that intersects with a previous path is logged as an error (if a log file is named with the -file option) and ignored. An error also occurs if the -path option names a file or directory that the upserver process on the specified server machine is not directed to distribute. Because multiple upclient processes can be run on a single machine, a filename specified with the -file option must be distinct.

Finally, the machine running the upclient process must be named in the admin.up file on the machine running the upserver process (the machine specified with the -server option). Otherwise, the local machine's upclient process is not permitted to access files from the upserver process.

Privilege Required
You must be logged in as root on the local machine.

Examples
The following command starts the upclient process running on the local machine. The process is to check every 180 seconds (3 minutes) for changes to the binary files in the directory /rs_aix32/bin on the Binary Distribution machine named /.../abc.com/hosts/fs1. Errors are written to the file named /tmp/fs1/UpclientLog on the local disk of the machine running the upclient process.

$ upclient -s /.../abc.com/hosts/fs1 -p /rs_aix32/bin -t 180 -l /tmp/fs1/UpclientLog

Related Information
Commands: upserver(8dfs)

Files: admin.up(4dfs)