is taken from a list of system names that uucp
knows about. The destination system-name
can also be a list of names such as:
in which case, an attempt is made to send the file via the specified route to the destination. Care should be taken to ensure that intermediate nodes in the route are willing to forward information.
The shell pattern matching notation characters '?'
, and "[...]"
appearing in pathname
shall be expanded on the appropriate system.
Pathnames can be one of:
- An absolute pathname.
- A pathname preceded by ~user where user is a login name on the specified system and is replaced by that user's login directory. Note that if an invalid login is specified, the default is to the public directory (called PUBDIR; the actual location of PUBDIR is implementation-defined).
- A pathname preceded by ~/destination where destination is appended to PUBDIR.
- This destination is treated as a filename unless more than one file is being transferred by this request or the destination is already a directory. To ensure that it is a directory, follow the destination with a '/'. For example, ~/dan/ as the destination makes the directory PUBDIR/dan if it does not exist and puts the requested files in that directory.
- Anything else shall be prefixed by the current directory.
If the result is an erroneous pathname for the remote system, the copy shall fail. If the destination-file
is a directory, the last part of the source-file
name shall be used.
The read, write, and execute permissions given by uucp