NIO CommKit Host Interface Installation and System Administration Manual

PULL(1C) PULL(1C)
E-13 CommKit Host Interface, Release 4.0
NAME
pull – transfer files from another system
SYNOPSIS
pull [ -L ] destination filename ... directory
DESCRIPTION
pull establishes an AT&T data switch circuit to a source (remote) host named in destination and transfers
files from that host.
The filenames are files or directories on the source machine and are interpreted relative to the user’s HOME
directory on the source destination if they do not begin with a ’/’. The filenames are placed in the directory
on the target (local) machine. If the directory does not begin with a ’/’ it is interpreted relative to the current
directory. 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.
pull 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 local machine is root; otherwise, the files
will be owned by the current user.
pull preserves the name, type and contents of the files it moves with the following exceptions.
Long Names If 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 name will
be truncated to 14 characters. The local side will warn the user for each file name that
is truncated.
Symbolic Links Files of type symbolic link will be preserved unless the –L option is used. 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, the source machine will be
asked to 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. If, in following a path that contains a symbolic
link that points to a directory, the source machine finds a directory that has already
been transferred, it will not transfer it a second time. The source however, will always
transfer directories in a path that does not contain a symbolic link even if that directory
has already been transferred while following a path that does contain a symbolic link.
In both cases, the source machine will warn the user for every affected directory.
The push(1C) and pull commands invoke the pupu program (/opt/dk/bin/pupu) on the remote system to
handle the remote end of all file transfers. If the srvtab(4) file on the remote system invokes the pupu program
with the -r option, file transfers will be restricted to/from the home directory tree on the remote system by
disallowing all paths that begin with a leading ’/’ or that contain an embedded ’..’ specification. In this
restricted mode, only transfers containing PATHs relative to the HOME directory will be accepted.
Multiple Interfaces
If multiple interface boards are installed on the originating host, the pull command will use the default
processing to select the interface for the out-going call. See dkdial(3X) and authorize(1M) for more
information.
WARNINGS
If the source destination is identical to the target host and the source directory is identical to the target
directory, then the pull command will overwrite filename and its contents may be destroyed.
The modification times are preserved on transferred files as long as they are earlier in relative time (i.e.,
seconds since the 00:00:00 GMT, January 1, 1970, epoch) than the current relative time on the local machine.