Installation & Configuration |
Aspera handles symbolic links in IBM Aspera Sync based on settings configured in the aspera.conf file, found in the following location:
/opt/aspera/etc/aspera.conf
<file_system> <symbolic_links>comma-separated_options</symbolic_links> </file_system>
Option | Description | Client Behavior | Server Behavior |
---|---|---|---|
create | Create symbolic links with arbitrary targets. This is the default. | Disallowed
if not configured. Note: Servers running on a Windows platform will always reject such a request, regardless of the option configured. |
Symbolic links are always copied to the server if the client requests. |
follow | Follow symbolic links with targets inside docroot. If at any point the path goes outside the docroot, Aspera Sync will not complete the transfer. This is option set by default. | Symbolic links are always copied to the server if the client requests.
Note: If the docroot is a symbolic link and is specified as the source or destination: As the receiver, follow the target widely (no docroot constraint) and unconditionally, regardless of the symbolic link actions that are configured/requested. |
|
follow_wide | Follow symbolic links with arbitrary targets, even if the targets are outside the docroot. | Disallowed if not configured, except for Windows servers.
Follow symbolic links anywhere without docroot constraint. Note: If the docroot is a symbolic link and is specified as the source or destination: As sender, follow the target unconditionally, regardless of the symbolic link actions that are configured/requested. |
|
none | Take no action with symbolic links. | Take no action with symbolic links. | Take no action with symbolic links. |