| Main index | Section 1 (General commands) | [日本語] | [한국인] | [Deutsch] | options | ||
|
|
|||||||
The following options are available:
| | |
|
If the
| |
| | |
|
If the
| |
| | |
|
If the
| |
| | |
|
If
source_file
designates a directory,
cp
copies the directory and the entire subtree connected at that point.
If the
source_file
ends in a
/,
the contents of the directory are copied rather than the
directory itself.
This option also causes symbolic links to be copied, rather than
indirected through, and for
cp
to create special files rather than copying them as normal files.
Created directories have the same mode as the corresponding source
directory, unmodified by the process' umask.
Note that cp copies hard linked files as separate files. If you need to preserve hard links, consider using tar(1), cpio(1), or pax(1) instead. | |
| | |
|
Archive mode.
Same as
| |
| | |
|
For each existing destination pathname, remove it and
create a new file, without prompting for confirmation
regardless of its permissions.
(The
| |
| | |
|
Cause
cp
to write a prompt to the standard error output before copying a file
that would overwrite an existing file.
If the response from the standard input begins with the character
'y'
or
'Y',
the file copy is attempted.
(The
| |
| | |
| Create hard links to regular files in a hierarchy instead of copying. | |
| | |
|
Do not overwrite an existing file.
(The
| |
| | |
|
Cause
cp
to preserve the following attributes of each source
file in the copy: modification time, access time,
file flags, file mode, user ID, and group ID, as allowed by permissions.
If the user ID and group ID cannot be preserved, no error message is displayed and the exit value is not altered. If the source file has its set-user-ID bit on and the user ID cannot be preserved, the set-user-ID bit is not preserved in the copy's permissions. If the source file has its set-group-ID bit on and the group ID cannot be preserved, the set-group-ID bit is not preserved in the copy's permissions. If the source file has both its set-user-ID and set-group-ID bits on, and either the user ID or group ID cannot be preserved, neither the set-user-ID nor set-group-ID bits are preserved in the copy's permissions. | |
| | |
| Cause cp to be verbose, showing files as they are copied. | |
For each destination file that already exists, its contents are
overwritten if permissions allow.
Its mode, user ID, and group
ID are unchanged unless the
In the second synopsis form,
target_directory
must exist unless there is only one named
source_file
which is a directory and the
If the destination file does not exist, the mode of the source file is used as modified by the file mode creation mask ( umask, see csh(1)). If the source file has its set-user-ID bit on, that bit is removed unless both the source file and the destination file are owned by the same user. If the source file has its set-group-ID bit on, that bit is removed unless both the source file and the destination file are in the same group and the user is a member of that group. If both the set-user-ID and set-group-ID bits are set, all of the above conditions must be fulfilled or both bits are removed.
Appropriate permissions are required for file creation or overwriting.
Symbolic links are always followed unless the
If cp receives a SIGINFO (see the status argument for stty(1)) signal, the current input and output file and the percentage complete will be written to the standard output.
The
| CP (1) | October 27, 2006 |
| Main index | Section 1 (General commands) | [日本語] | [한국인] | [Deutsch] | options | ||
|
|
|||||||
Please direct any comments about this manual page service to this message board.
| “ | "I liken starting one's computing career with Unix, say as an undergraduate, to being born in East Africa. It is intolerably hot, your body is covered with lice and flies, you are malnourished and you suffer from numerous curable diseases. But, as far as young East Africans can tell, this is simply the natural condition and they live within it. By the time they find out differently, it is too late. They already think that the writing of shell scripts is a natural act." | ” |
| — Ken Pier, Xerox PARC | ||