UUCP

The uucp utility shall copy files named by the source-file argument to the destination-file argument. The files named can be on local or remote systems. The uucp utility cannot guarantee support for all character encodings in all circumstances. For example, transmission data may be restricted to 7 bits by the underlying network, 8-bit data and filenames need not be portable to non-internationalized systems, and so on. Under these circumstances, it is recommended that only characters defined in the ISO/IEC 646:1991 standard International Reference Version (equivalent to ASCII) 7-bit range of characters be used, and that only characters defined in the portable filename character set be used for naming files. The protocol for transfer of files is unspecified by POSIX.1-2017. Typical implementations of this utility require a communications line configured to use XBD General Terminal Interface , but other communications means may be used. On systems where there are no available communications means (either temporarily or permanently), this utility shall write an error message describing the problem and exit with a non-zero exit status. Do not copy local file to the spool directory for transfer to the remote machine (default). Force the copy of local files to the spool directory for transfer. Write the job identification string to standard output. This job identification can be used by uustat to obtain the status or terminate a job. Provide a default value for the internationalization variables that are unset or null. (See XBD Internationalization Variables for the precedence of internationalization variables used to determine the values of locale categories.) If set to a non-empty string value, override the values of all the other internationalization variables. Determine the locale for the behavior of ranges, equivalence classes, and multi-character collating elements within bracketed filename patterns. Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multi-byte characters in arguments and input files) and the behavior of character classes within bracketed filename patterns (for example, "'[[:lower:]] '" ). Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error, and informative messages written to standard output. Determine the location of message catalogs for the processing of LC MESSAGES. The output files (which may be on other systems) are copies of the input files. This utility is part of the UUCP Utilities option and need not be supported by all implementations. The domain of remotely accessible files can (and for obvious security reasons usually should) be severely restricted. As noted above, shell metacharacters appearing in pathnames are expanded on the appropriate system. On an internationalized system, this is done under the control of local settings of LC COLLATE and LC CTYPE. Thus, care should be taken when using bracketed filename patterns, as collation and typing rules may vary from one system to another. Also be aware that certain types of expression (that is, equivalence classes, character classes, and collating symbols) need not be supported on non-internationalized systems. The LC TIME and TZ entries are removed from the ENVIRONMENT VARIABLES section. SD5-XCU-ERN-46 is applied, moving this utility to the UUCP Utilities Option Group.