]> git.saurik.com Git - apple/file_cmds.git/blame_incremental - cp/cp.1
file_cmds-212.1.tar.gz
[apple/file_cmds.git] / cp / cp.1
... / ...
CommitLineData
1.\"-
2.\" Copyright (c) 1989, 1990, 1993, 1994
3.\" The Regents of the University of California. All rights reserved.
4.\"
5.\" This code is derived from software contributed to Berkeley by
6.\" the Institute of Electrical and Electronics Engineers, Inc.
7.\"
8.\" Redistribution and use in source and binary forms, with or without
9.\" modification, are permitted provided that the following conditions
10.\" are met:
11.\" 1. Redistributions of source code must retain the above copyright
12.\" notice, this list of conditions and the following disclaimer.
13.\" 2. Redistributions in binary form must reproduce the above copyright
14.\" notice, this list of conditions and the following disclaimer in the
15.\" documentation and/or other materials provided with the distribution.
16.\" 4. Neither the name of the University nor the names of its contributors
17.\" may be used to endorse or promote products derived from this software
18.\" without specific prior written permission.
19.\"
20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
32.\" @(#)cp.1 8.3 (Berkeley) 4/18/94
33.\" $FreeBSD: src/bin/cp/cp.1,v 1.33 2005/02/25 00:40:46 trhodes Exp $
34.\"
35.Dd February 23, 2005
36.Dt CP 1
37.Os
38.Sh NAME
39.Nm cp
40.Nd copy files
41.Sh SYNOPSIS
42.Nm cp
43.Oo
44.Fl R
45.Op Fl H | Fl L | Fl P
46.Oc
47.Op Fl fi | n
48.Op Fl apvX
49.Ar source_file target_file
50.Nm cp
51.Oo
52.Fl R
53.Op Fl H | Fl L | Fl P
54.Oc
55.Op Fl fi | n
56.Op Fl apvX
57.Ar source_file ... target_directory
58.Sh DESCRIPTION
59In the first synopsis form, the
60.Nm cp
61utility copies the contents of the
62.Ar source_file
63to the
64.Ar target_file .
65In the second synopsis form,
66the contents of each named
67.Ar source_file
68is copied to the destination
69.Ar target_directory .
70The names of the files themselves are not changed.
71If
72.Nm cp
73detects an attempt to copy a file to itself, the copy will fail.
74.Pp
75The following options are available:
76.Bl -tag -width flag
77.It Fl a
78Same as
79.Fl pPR
80options. Preserves structure and attributes of files
81but not directory structure.
82.It Fl f
83.\"For each existing destination pathname, remove it and
84If the destination file cannot be opened, remove it and
85create a new file, without prompting for confirmation
86regardless of its permissions.
87(The
88.Fl f
89option overrides any previous
90.Fl n
91option.)
92.Pp
93The target file is not unlinked before the copy.
94Thus, any existing access rights will be retained.
95.It Fl H
96If the
97.Fl R
98option is specified, symbolic links on the command line are followed.
99(Symbolic links encountered in the tree traversal are not followed.)
100.It Fl i
101Cause
102.Nm cp
103to write a prompt to the standard error output before copying a file
104that would overwrite an existing file.
105If the response from the standard input begins with the character
106.Sq Li y
107or
108.Sq Li Y ,
109the file copy is attempted.
110(The
111.Fl i
112option overrides any previous
113.Fl n
114option.)
115.It Fl L
116If the
117.Fl R
118option is specified, all symbolic links are followed.
119.It Fl n
120Do not overwrite an existing file.
121(The
122.Fl n
123option overrides any previous
124.Fl f
125or
126.Fl i
127options.)
128.It Fl P
129If the
130.Fl R
131option is specified, no symbolic links are followed.
132This is the default.
133.It Fl p
134Cause
135.Nm cp
136to preserve the following attributes of each source
137file in the copy: modification time, access time,
138file flags, file mode, user ID, and group ID, as allowed by permissions.
139Access Control Lists (ACLs) and Extended Attributes (EAs),
140including resource forks, will also be preserved.
141.Pp
142If the user ID and group ID cannot be preserved, no error message
143is displayed and the exit value is not altered.
144.Pp
145If the source file has its set-user-ID bit on and the user ID cannot
146be preserved, the set-user-ID bit is not preserved
147in the copy's permissions.
148If the source file has its set-group-ID bit on and the group ID cannot
149be preserved, the set-group-ID bit is not preserved
150in the copy's permissions.
151If the source file has both its set-user-ID and set-group-ID bits on,
152and either the user ID or group ID cannot be preserved, neither
153the set-user-ID nor set-group-ID bits are preserved in the copy's
154permissions.
155.It Fl R
156If
157.Ar source_file
158designates a directory,
159.Nm cp
160copies the directory and the entire subtree connected at that point.
161If the
162.Ar source_file
163ends in a
164.Pa / ,
165the contents of the directory are copied rather than the
166directory itself.
167This option also causes symbolic links to be copied, rather than
168indirected through, and for
169.Nm cp
170to create special files rather than copying them as normal files.
171Created directories have the same mode as the corresponding source
172directory, unmodified by the process' umask.
173.Pp
174In
175.Fl R
176mode,
177.Nm cp
178will continue copying even if errors are detected.
179.Pp
180Note that
181.Nm cp
182copies hard-linked files as separate files.
183If you need to preserve hard links, consider using
184.Xr tar 1 ,
185.Xr cpio 1 ,
186or
187.Xr pax 1
188instead.
189.It Fl v
190Cause
191.Nm cp
192to be verbose, showing files as they are copied.
193.It Fl X
194Do not copy Extended Attributes (EAs) or resource forks.
195.El
196.Pp
197For each destination file that already exists, its contents are
198overwritten if permissions allow.
199Its mode, user ID, and group
200ID are unchanged unless the
201.Fl p
202option was specified.
203.Pp
204In the second synopsis form,
205.Ar target_directory
206must exist unless there is only one named
207.Ar source_file
208which is a directory and the
209.Fl R
210flag is specified.
211.Pp
212If the destination file does not exist, the mode of the source file is
213used as modified by the file mode creation mask
214.Pf ( Ic umask ,
215see
216.Xr csh 1 ) .
217If the source file has its set-user-ID bit on, that bit is removed
218unless both the source file and the destination file are owned by the
219same user.
220If the source file has its set-group-ID bit on, that bit is removed
221unless both the source file and the destination file are in the same
222group and the user is a member of that group.
223If both the set-user-ID and set-group-ID bits are set, all of the above
224conditions must be fulfilled or both bits are removed.
225.Pp
226Appropriate permissions are required for file creation or overwriting.
227.Pp
228Symbolic links are always followed unless the
229.Fl R
230flag is set, in which case symbolic links are not followed, by default.
231The
232.Fl H
233or
234.Fl L
235flags (in conjunction with the
236.Fl R
237flag) cause symbolic links to be followed as described above.
238The
239.Fl H ,
240.Fl L
241and
242.Fl P
243options are ignored unless the
244.Fl R
245option is specified.
246In addition, these options override each other and the
247command's actions are determined by the last one specified.
248.Pp
249If
250.Nm cp
251receives a
252.Dv SIGINFO
253(see the
254.Cm status
255argument for
256.Xr stty 1 )
257signal, the current input and output file and the percentage complete
258will be written to the standard output.
259.Sh EXIT STATUS
260.Ex -std
261.Sh COMPATIBILITY
262Historic versions of the
263.Nm cp
264utility had a
265.Fl r
266option.
267This implementation supports that option;
268however, its use is strongly discouraged,
269as it does not correctly copy special files, symbolic links, or fifo's.
270.Pp
271The
272.Fl v
273and
274.Fl n
275options are non-standard and their use in scripts is not recommended.
276.Sh LEGACY DESCRIPTION
277In legacy mode,
278.Fl f
279will override
280.Fl i .
281Also, under the
282.Fl f
283option, the target file is always unlinked before the copy.
284Thus, new access rights will always be set.
285.Pp
286In
287.Fl R
288mode, copying will terminate if an error is encountered.
289.Pp
290For more information about legacy mode, see
291.Xr compat 5 .
292.Sh SEE ALSO
293.Xr mv 1 ,
294.Xr rcp 1 ,
295.Xr umask 2 ,
296.Xr fts 3 ,
297.Xr compat 5 ,
298.Xr symlink 7
299.Sh STANDARDS
300The
301.Nm cp
302command is expected to be
303.St -p1003.2
304compatible.
305.Sh HISTORY
306A
307.Nm cp
308command appeared in
309.At v1 .