AutoSYNC Software User's Guide (Update 18)

Installation
HP AutoSYNC User’s Guide—522580-019
2-10
Special Cases: Privileged Synchronization
Processes
For details on configuring and using an alternate environment, see Configuring and
Using an Alternate AutoSYNC Environment on page A-7.
Special Cases: Privileged Synchronization
Processes
Certain synchronization file sets may require the use of a privileged ASYSYNC or
ASYSYNCP process:

If, on the source system, the AutoSYNC Authorizer does not have the privileges to
“log down” as another user ID, one of the options is to license the local
ASYSYNCP process. See Bypassing Disabled Log Down on page 4-7 for details.

For the synchronization of file sets that contain object files with license or progid
attributes, ASYSYNC (or ASYSYNCP if synchronizing over TCP/IP) on the
destination system must operate under a local user ID. A local user ID is required
to perform both scheduled and one-time synchronizations. See Preserving Security
Attributes on the Destination on page 3-19 for details.

To set the owner of a synchronized symbolic link to a user different than the user
performing the synchronization or to give the link to the user ID specified through
the OWNER or OWNERGROUP option, the destination ASYSYNC process (or the
destination ASYSYNCP if synchronizing over TCP/IP) has to be privileged. See
Ownership of Symbolic Links on page 5-7.

To synchronize OSS file sets on a remote system as SUPER.SUPER and allow
SUPER.SUPER to change the ownership of the OSS files. See Ownership of OSS
Files on page 5-6 for details.