Owner's manual

OSS File Synchronization
HP AutoSYNC User’s Guide—522580-015
5-6
Changing Default Ownership of Symbolic Links
or directory but did not have WRITE access to the source file set, WRITE access on
the destination OSS files is set as follows:
•
If the user is not SUPER.SUPER (255,255), WRITE access is granted for the
destination file. AutoSYNC applies the equivalent of Guardian purge security rules
to OSS WRITE security.
•
If the user is SUPER.SUPER (255,255), WRITE security is not upgraded and
remains the same as the source file security setting because the SUPER.SUPER
user always has the required WRITE access.
You may use the SECURE option to override the default security setting.
The SECURE option for OSS files specifies read, write and execute access, for the
user (owner of the file or directory), the group and others: “rwxrwxrwx”. The complete
security string must be entered. The accepted values are:
•
“r” grants read access
•
“w” grants write access
•
“x” grants execute access
•
“-” denies access for read, write, and execute settings.
Ownership of synchronized symbolic links is a special case. By default, the owner of a
synchronized symbolic link is always the user and not the owner of the source
symbolic link or the OWNER specified in the SYNCHRONIZE command option.
Likewise, the group ID of synchronized symbolic links is, by default, the group ID of the
user and not the group ID of the source symbolic link or the group ID specified in the
SYNCHRONIZE command OWNERGROUP option.
You can change this behavior as described below.
Changing Default Ownership of Symbolic Links
To set the owner of a synchronized symbolic link to a user different than the user
performing the synchronization or to set the owner to the user ID specified through the
OWNER or OWNERGROUP option, the remote ASYSYNC process (or the remote
ASYSYNCP if synchronizing over TCP/IP) has to be privileged. A privileged ASYSYNC
(or ASYSYNCP if synchronizing over TCP/IP) enables AutoSYNC to switch to the user
ID of the source symbolic link or to the specified OWNER when AutoSYNC creates the
link.
This feature is only supported if the user is SUPER.SUPER (255,255).
To make the remote ASYSYNC a privileged process (or remote ASYSYNCP if
synchronizing over TCP/IP), perform the following steps on the remote system after the
files have been moved to the AUTOSYNC subvolume: