NIO CommKit Host Interface Installation and System Administration Manual

PUSH(1C) PUSH(1C)
E-15 CommKit Host Interface, Release 4.0
NAME
push – transfer files to another system
SYNOPSIS
push [ –L ] destination filename ... directory
push [ -L ] destination–directory < file_list
DESCRIPTION
push establishes an AT&T data switch circuit to the target (remote) host named in destination and transfers
files to that host.
The filenames are files or directories on the source (local) machine. The filenames are placed in the directory
on the target machine. If the directory does not begin with a ’/’, it is interpreted relative to the user’s HOME
directory on the target destination. The directory will be created, if required, before the files are transferred.
Specifying a directory as one of the filenames will transfer the entire directory tree beginning at the named
point.
The second command format takes the list of files to transfer from the standard input. It differs from the first
format, however, in that the position of the files in input pathnames is preserved. For example,
push lxho9 a/b c a/d/e /tmp/one
creates files /tmp/one/b, /tmp/one/c, and /tmp/one/e, while
push lxho9 - /tmp/two <<!
a/b
c
a/d/e
!
creates files /tmp/two/a/b, /tmp/two/c, and /tmp/two/a/d/e. The second format is useful in combination with
find(1) to select portions of a directory tree to transfer.
push preserves the file modes and modification times of the files it moves. The original file owner (numeric
user ID) is preserved if the effective user ID of the process on the target machine is root. Otherwise the files
will be owned by the user’s login on the target host.
push preserves the name, type and contents of the files it moves with the following exceptions.
Long Names If the target machine is a SVR4 implementation but the target file system does not support
file names greater than 14 characters and the source machine transfers a file with a name
greater then 14 characters, the file name will be truncated to 14 characters. The remote side
will warn the user for each file name that is truncated.
Long Names If the target machine is not a SVR4 implementation and the source machine transfers a file
with a name greater then 14 characters, the name will usually be truncated to 14 characters.
Note: A few pre-SVR4 implementations support long file names but the push command
has no way of knowing if these systems do or do not. The local side will warn the user for
each file name that may be truncated.
Symbolic Links Files of type symbolic link will be preserved unless the –L option is used or the target
machine does not support symbolic links. A transferred symbolic link will be identical to
the source file; it may, however, have a different context in the target environment.
If the –L option is used or the target machine does not support symbolic links, the source
machine will follow symbolic links with the following behaviors: The symbolic link will
be treated as if it were the file type of the file pointed to. If the file does not exist or the user
does not have permission to access the file, no transfer will take place and the source
machine will issue a warning.