logo

oasis-root

Compiled tree of Oasis Linux based on own branch at <https://hacktivis.me/git/oasis/> git clone https://anongit.hacktivis.me/git/oasis-root.git

uucp.1p (9097B)


  1. '\" et
  2. .TH UUCP "1P" 2017 "IEEE/The Open Group" "POSIX Programmer's Manual"
  3. .\"
  4. .SH PROLOG
  5. This manual page is part of the POSIX Programmer's Manual.
  6. The Linux implementation of this interface may differ (consult
  7. the corresponding Linux manual page for details of Linux behavior),
  8. or the interface may not be implemented on Linux.
  9. .\"
  10. .SH NAME
  11. uucp
  12. \(em system-to-system copy
  13. .SH SYNOPSIS
  14. .LP
  15. .nf
  16. uucp \fB[\fR-cCdfjmr\fB] [\fR-n \fIuser\fB] \fIsource-file\fR... \fIdestination-file\fR
  17. .fi
  18. .SH DESCRIPTION
  19. The
  20. .IR uucp
  21. utility shall copy files named by the
  22. .IR source-file
  23. argument to the
  24. .IR destination-file
  25. argument. The files named can be on local or remote systems.
  26. .P
  27. The
  28. .IR uucp
  29. utility cannot guarantee support for all character encodings in all
  30. circumstances. For example, transmission data may be restricted to 7
  31. bits by the underlying network, 8-bit data and filenames need not be
  32. portable to non-internationalized systems, and so on. Under these
  33. circumstances, it is recommended that only characters defined in the
  34. ISO/IEC\ 646:\|1991 standard International Reference Version (equivalent to ASCII) 7-bit range
  35. of characters be used, and that only characters defined in the portable
  36. filename character set be used for naming files. The protocol for
  37. transfer of files is unspecified by POSIX.1\(hy2008.
  38. .P
  39. Typical implementations of this utility require a communications line
  40. configured to use the Base Definitions volume of POSIX.1\(hy2017,
  41. .IR "Chapter 11" ", " "General Terminal Interface",
  42. but other communications means may be used. On systems where there are
  43. no available communications means (either temporarily or permanently),
  44. this utility shall write an error message describing the problem and
  45. exit with a non-zero exit status.
  46. .SH OPTIONS
  47. The
  48. .IR uucp
  49. utility shall conform to the Base Definitions volume of POSIX.1\(hy2017,
  50. .IR "Section 12.2" ", " "Utility Syntax Guidelines".
  51. .P
  52. The following options shall be supported:
  53. .IP "\fB\-c\fP" 10
  54. Do not copy local file to the spool directory for transfer to the
  55. remote machine (default).
  56. .IP "\fB\-C\fP" 10
  57. Force the copy of local files to the spool directory for transfer.
  58. .IP "\fB\-d\fP" 10
  59. Make all necessary directories for the file copy (default).
  60. .IP "\fB\-f\fP" 10
  61. Do not make intermediate directories for the file copy.
  62. .IP "\fB\-j\fP" 10
  63. Write the job identification string to standard output. This job
  64. identification can be used by
  65. .IR uustat
  66. to obtain the status or terminate a job.
  67. .IP "\fB\-m\fP" 10
  68. Send mail to the requester when the copy is completed.
  69. .IP "\fB\-n\ \fIuser\fR" 10
  70. Notify
  71. .IR user
  72. on the remote system that a file was sent.
  73. .IP "\fB\-r\fP" 10
  74. Do not start the file transfer; just queue the job.
  75. .SH OPERANDS
  76. The following operands shall be supported:
  77. .IP "\fIdestination-file\fR,\ \fIsource-file\fR" 10
  78. .br
  79. A pathname of a file to be copied to, or from, respectively. Either
  80. name can be a pathname on the local machine, or can have the form:
  81. .RS 10
  82. .sp
  83. .RS 4
  84. .nf
  85. \fIsystem-name\fR!\fIpathname\fR
  86. .fi
  87. .P
  88. .RE
  89. .P
  90. where
  91. .IR system-name
  92. is taken from a list of system names that
  93. .IR uucp
  94. knows about.
  95. The destination
  96. .IR system-name
  97. can also be a list of names such as:
  98. .sp
  99. .RS 4
  100. .nf
  101. \fIsystem-name\fR!\fIsystem-name\fR!...!\fIsystem-name\fR!\fIpathname\fR
  102. .fi
  103. .P
  104. .RE
  105. .P
  106. in which case, an attempt is made to send the file via the specified
  107. route to the destination. Care should be taken to ensure that
  108. intermediate nodes in the route are willing to forward information.
  109. .P
  110. The shell pattern matching notation characters
  111. .BR '?' ,
  112. .BR '*' ,
  113. and
  114. .BR \(dq[...]\(dq
  115. appearing in
  116. .IR pathname
  117. shall be expanded on the appropriate system.
  118. .P
  119. Pathnames can be one of:
  120. .IP " 1." 4
  121. An absolute pathname.
  122. .IP " 2." 4
  123. A pathname preceded by ~\c
  124. .IR user
  125. where
  126. .IR user
  127. is a login name on the specified system and is replaced by that user's
  128. login directory. Note that if an invalid login is specified, the
  129. default is to the public directory (called
  130. .IR PUBDIR ;
  131. the actual location of
  132. .IR PUBDIR
  133. is implementation-defined).
  134. .IP " 3." 4
  135. A pathname preceded by ~/\c
  136. .IR destination
  137. where
  138. .IR destination
  139. is appended to
  140. .IR PUBDIR .
  141. .RS 4
  142. .TP 10
  143. .BR Note:
  144. This destination is treated as a filename unless more than one file is
  145. being transferred by this request or the destination is already a
  146. directory. To ensure that it is a directory, follow the destination
  147. with a
  148. .BR '/' .
  149. For example,
  150. .BR ~/dan/
  151. as the destination makes the directory
  152. .BR PUBDIR/dan
  153. if it does not exist and puts the requested files in that directory.
  154. .P
  155. .RE
  156. .IP " 4." 4
  157. Anything else shall be prefixed by the current directory.
  158. .P
  159. If the result is an erroneous pathname for the remote system, the copy
  160. shall fail. If the
  161. .IR destination-file
  162. is a directory, the last part of the
  163. .IR source-file
  164. name shall be used.
  165. .P
  166. The read, write, and execute permissions given by
  167. .IR uucp
  168. are implementation-defined.
  169. .RE
  170. .SH STDIN
  171. Not used.
  172. .SH "INPUT FILES"
  173. The files to be copied are regular files.
  174. .SH "ENVIRONMENT VARIABLES"
  175. The following environment variables shall affect the execution of
  176. .IR uucp :
  177. .IP "\fILANG\fP" 10
  178. Provide a default value for the internationalization variables that are
  179. unset or null. (See the Base Definitions volume of POSIX.1\(hy2017,
  180. .IR "Section 8.2" ", " "Internationalization Variables"
  181. for the precedence of internationalization variables used to determine
  182. the values of locale categories.)
  183. .IP "\fILC_ALL\fP" 10
  184. If set to a non-empty string value, override the values of all the
  185. other internationalization variables.
  186. .IP "\fILC_COLLATE\fP" 10
  187. .br
  188. Determine the locale for the behavior of ranges, equivalence classes,
  189. and multi-character collating elements within bracketed filename
  190. patterns.
  191. .IP "\fILC_CTYPE\fP" 10
  192. Determine the locale for the interpretation of sequences of bytes of
  193. text data as characters (for example, single-byte as opposed to
  194. multi-byte characters in arguments and input files) and the behavior of
  195. character classes within bracketed filename patterns (for example,
  196. .BR \(dq\(aq[[:lower:]]*\(aq\(dq ).
  197. .IP "\fILC_MESSAGES\fP" 10
  198. .br
  199. Determine the locale that should be used to affect the format and
  200. contents of diagnostic messages written to standard error, and
  201. informative messages written to standard output.
  202. .IP "\fINLSPATH\fP" 10
  203. Determine the location of message catalogs for the processing of
  204. .IR LC_MESSAGES .
  205. .SH "ASYNCHRONOUS EVENTS"
  206. Default.
  207. .SH STDOUT
  208. Not used.
  209. .SH STDERR
  210. The standard error shall be used only for diagnostic messages.
  211. .SH "OUTPUT FILES"
  212. The output files (which may be on other systems) are copies of the
  213. input files.
  214. .P
  215. If
  216. .BR \-m
  217. is used, mail files are modified.
  218. .SH "EXTENDED DESCRIPTION"
  219. None.
  220. .SH "EXIT STATUS"
  221. The following exit values shall be returned:
  222. .IP "\00" 6
  223. Successful completion.
  224. .IP >0 6
  225. An error occurred.
  226. .SH "CONSEQUENCES OF ERRORS"
  227. Default.
  228. .LP
  229. .IR "The following sections are informative."
  230. .SH "APPLICATION USAGE"
  231. This utility is part of the UUCP Utilities option and need not be
  232. supported by all implementations.
  233. .P
  234. The domain of remotely accessible files can (and for obvious security
  235. reasons usually should) be severely restricted.
  236. .P
  237. Note that the
  238. .BR '!'
  239. character in addresses has to be escaped when using
  240. .IR csh
  241. as a command interpreter because of its history substitution syntax.
  242. For
  243. .IR ksh
  244. and
  245. .IR sh
  246. the escape is not necessary, but may be used.
  247. .P
  248. As noted above, shell metacharacters appearing in pathnames are
  249. expanded on the appropriate system. On an internationalized system,
  250. this is done under the control of local settings of
  251. .IR LC_COLLATE
  252. and
  253. .IR LC_CTYPE .
  254. Thus, care should be taken when using bracketed filename patterns, as
  255. collation and typing rules may vary from one system to another. Also
  256. be aware that certain types of expression (that is, equivalence
  257. classes, character classes, and collating symbols) need not be
  258. supported on non-internationalized systems.
  259. .SH EXAMPLES
  260. None.
  261. .SH RATIONALE
  262. None.
  263. .SH "FUTURE DIRECTIONS"
  264. None.
  265. .SH "SEE ALSO"
  266. .IR "\fImailx\fR\^",
  267. .IR "\fIuuencode\fR\^",
  268. .IR "\fIuustat\fR\^",
  269. .IR "\fIuux\fR\^"
  270. .P
  271. The Base Definitions volume of POSIX.1\(hy2017,
  272. .IR "Chapter 8" ", " "Environment Variables",
  273. .IR "Chapter 11" ", " "General Terminal Interface",
  274. .IR "Section 12.2" ", " "Utility Syntax Guidelines"
  275. .\"
  276. .SH COPYRIGHT
  277. Portions of this text are reprinted and reproduced in electronic form
  278. from IEEE Std 1003.1-2017, Standard for Information Technology
  279. -- Portable Operating System Interface (POSIX), The Open Group Base
  280. Specifications Issue 7, 2018 Edition,
  281. Copyright (C) 2018 by the Institute of
  282. Electrical and Electronics Engineers, Inc and The Open Group.
  283. In the event of any discrepancy between this version and the original IEEE and
  284. The Open Group Standard, the original IEEE and The Open Group Standard
  285. is the referee document. The original Standard can be obtained online at
  286. http://www.opengroup.org/unix/online.html .
  287. .PP
  288. Any typographical or formatting errors that appear
  289. in this page are most likely
  290. to have been introduced during the conversion of the source files to
  291. man page format. To report such errors, see
  292. https://www.kernel.org/doc/man-pages/reporting_bugs.html .