IBM Aspera HST Admin Manual page 225

asconfigurator option
aspera.conf setting
async_enabled
<async_enabled>
async_log_dir
<async_log_dir>
async_log_level
<async_log_level>
async_session_timeout
<async_session_timeout>
directory_create_mode
<directory_create_mode>
directory_create_grant_mask
<directory_create_grant_mask>
preserve_acls
preserve_xattrs
<preserve_acls>
<preserve_xattrs>
Description and Value Options
Enable (set to true, default) or disable (set to false) Sync. When set
to false, the client async session fails with the error "Operation
'sync' not enabled or not permitted by license".
Specify an alternative location for the async server's log files. If unspecified,
log files are saved in the default location or the location that is specified by
the client with the -R option. For information on the default log file location,
see Logging on page 264.
Set the amount of detail in the async server activity log. Valid values are
log (default), dbg1, or dbg2.
The number of seconds async waits for a non-responsive session to resume
before it terminates. Value is a positive integer. (Default: 20)
Specify the directory creation mode (permissions). If specified,
create directories with these permissions irrespective of
<directory_create_grant_mask> and permissions of the directory
on the source computer. This option is applied only when the server is a
Unix-based receiver.
Value is a positive integer (octal). (Default: undefined)
Specify the mode for newly created directories if
directory_create_mode is not specified. If specified, directory
modes are set to their original modes plus the grant mask values. This
option is applied only when the server is a Unix-based receiver and when
directory_create_mode is not specified.
Value is a positive integer (octal). (Default: 755)
Specify if the ACL access data (acls) or extended attributes (xattrs)
from Windows or macOS files are preserved. Three modes are supported.
(Default: none)
native: acls or xattrs are preserved by using the native capabilities
of the file system. If the destination does not support acls or xattrs,
async generates an error and exits.
metafile: acls or xattrs are preserved in a separate file. The file
is in the same location and has same name, but has the added extension
.aspera-meta. The .aspera-meta files are platform-independent,
and files can be reverted to native form if they are synchronized with a
compatible system.
none: No acls or xattrs data is preserved. This mode is supported on
all file systems.
ACL preservation is only meaningful if both hosts are in the same domain.
If a SID (security ID) in a source file does not exist at a destination, the sync
proceeds but no ACL data is saved and the log records that the ACL was not
applied.
The aspera.conf settings for acls or xattrs can be overwritten
by using the --preserve-acls or --preserve-xattrs options,
respectively, in a command-line async session.
| Aspera Sync | 225