pax.1 (2010 09)

p
pax(1) pax(1)
specified while creating the archive, the HFS file has optional ACL entries and the ACL
entries are good.
security.aclv
Indicates that the optional ACL entry for the file has been backed up for JFS files and its
value will be equal to 1. This record is written to the extended header if
-A option is
specified while creating the archive, the JFS file has optional ACL entries and the ACL
entries are good.
security.acl_nacl
The number of ACL entries that have been written to the extended header. This is common
to both HFS and JFS. This record is written to the extended header if
-A option is specified
while creating the archive, the JFS file has optional ACL entries and the ACL entries are
good.
security.acl_entry
The ACL entries for the file. This record is written to the extended header if
-A option is
specified while creating the archive, the file has optional ACL entries and the ACL entries
are good. The format for HFS ACL entries will be:
(a_uid,a_gid.a_mode)
The format for JFS ACL entries will be:
(a_type,a_uid/a_gid.a_perm)
However, the corresponding username/groupname of the uid/gid are written to the header.
If the value field is zero length, it shall delete any header block field, previously entered extended header
value, or global extended header value of the same name.
If a keyword in an extended header record (or in a
-o option-argument) overrides or deletes a
corresponding field in the
ustar header block, pax shall ignore the contents of that header block field.
Unlike the
ustar header block fields, NULLs shall not delimit value s; all characters within the value
field shall be considered data for the field. None of the length limitations of the
ustar header block fields
in
ustar Header Block shall apply to the extended header records.
pax Extended Header Keyword Precedence
This section describes the precedence in which the various header records and fields and command line
options are selected to apply to a file in the archive. When
pax is used in
read or list modes, it shall
determine a file attribute in the following sequence:
1. If
-o delete= keyword-prefix is used, the affected attributes shall be determined from Step 7., if
applicable, or ignored otherwise.
2. If
-o keyword:= is used, the affected attributes shall be ignored.
3. If
-o keyword:=value is used, the affected attribute shall be assigned the value .
4. If there is a
typeflag x extended header record, the affected attribute shall be assigned the value .
When extended header records conflict, the last one given in the header shall take precedence.
5. If
-o keyword=value is used, the affected attribute shall be assigned the value .
6. If there is a
typeflag g global extended header record, the affected attribute shall be assigned the
value . When global extended header records conflict, the last one given in the global header shall
take precedence.
7. Otherwise, the attribute shall be determined from the
ustar header block.
pax Extended Header File Times
The
pax utility shall write an mtime record for each file in write or copy modes if the file’s
modification time cannot be represented exactly in the ustar header logical record described in ustar
Interchange Format. This can occur if the time is out of ustar range, or if the file system of the under-
lying implementation supports non-integer time granularities and the time is not an integer. All of these
time records shall be formatted as a decimal representation of the time in seconds since the Epoch. If a
period (.) decimal point character is present, the digits to the right of the point shall represent the units
of a sub second timing granularity, where the first digit is tenths of a second and each subsequent digit is
a tenth of the previous digit.
12 Hewlett-Packard Company − 12 − HP-UX 11i Version 3: September 2010