Open System Services Shell and Utilities Reference Manual (G06.28+, H06.05+)

User Commands (c) cp(1)
The OSS Network File System (NFS) cannot access files that have ACLs. |
This table describes the impact of ACLs on the permissions used when a new file or directory is |
created by the cp command. Cases not included in the table represent impossible situations.
_______________________________________________________
cp Source Source Dest. Impact of
Command Fileset File/Dir Filesset ACLs on
Supports Supports Has Opt. Supports Permissions
ACLs ACLs ACLs ACLs of New File/Dir
_______________________________________________________
Y/N Y/N N N None
Y/N Y/N N Y See Note 2
Y/N Y Y N See Notes 1 and 3
N Y Y Y See Notes 1 and 2
Y Y Y Y See Note 4
_______________________________________________________
Note 1: The optional ACLs for the source file or directory are not copied to the
destination file or directory.
Note 2: If the destination parent directory has default ACL entries, those default
ACL entries are inherited by the new file or directory (see the acl(5)
reference page).
Note 3: If you use the -p flag, the file permissions are copied to the destination
file or directory and the class entry permissions in the ACL are used for
the destination file or directory group permissions. Otherwise, the per-
missions for the destination file or directory are set using the non-ACL
descriptions.
Note 4: If you use the -p flag, all ACL entries for the source file or directory are
copied to the destination file or directory. Otherwise, the permissions for
the destination file or directory are set using the non-ACL descriptions.
Use on Guardian Objects
Specify Guardian files with the /G pathname convention.
Only unstructured Guardian files are supported. If both the source and destination are Guardian
files, the file attributes specific to Guardian (such as extent sizes, file code, and file type) are
preserved. Thus if a type 101 EDIT Guardian file is copied within the Guardian volume, the tar-
get file is also a type 101 EDIT file, with all the line number information preserved. In addition,
if the -p flag is specified, other Guardian file attributes (such as user ID, file security, and times-
tamps) are preserved in the same manner they are preserved with the TACL command FUP DUP.
If you are copying a Guardian file to the OSS file hierarchy, only the content of the Guardian file
is copied: the Guardian file attributes are not preserved. Likewise, if you are copying an OSS
file to the Guardian file hierarchy, the target file is created as an unstructured Guardian file. Thus
if you copy a Guardian type 101 EDIT file to the OSS file hierarchy and then copy it back to the
Guardian file hierarchy, it will no longer be a Guardian type 101 EDIT file.
If a source file and destination file are determined to be the same, a diagnostic message is written
to the standard error file.
Because of the differences between the Guardian and OSS file systems, the following anomalies
can occur when OSS files are copied to a Guardian destination.
• A destination pathname can contain illegal /G filename characters, even after it
has been transformed into a /G pathname. As a result, the destination file cannot
be created on the Guardian destination, and the copy operation fails.
527188-007 Hewlett-Packard Company 2−73