Agents behave differently when encountering different types of file links depending on link type and operating system. Please refer to the table below for exact behavior.
Applicable to distribution and consolidation jobs only
Sync jobs don't sync symbolic links and junctions to prevent filename Conflicts. However, it's possible to follow a link on Linux Agents, read more about it here.If you want transfer jobs to ignore links and junctions, set Agent profile parameter "Ignore symlinks" to "Yes". Keep in mind that it will apply to all the jobs on the agent.
| Sync from | Link Type | Sync to | |||||
| Windows |
Linux |
Mac |
Azure |
Amazon |
GCP |
||
|
Windows |
hard link |
as file | as file | as file | as file | as file | as file |
| symlink to a file | as zero file | as zero file | as zero file | as zero file | as zero file | as zero file | |
| symlink to a folder | as folder | as folder | as folder | as folder | as folder | as folder | |
| directory junction | as folder | as folder | as folder | as folder | as folder | as folder | |
| Linux | hard link | as file | as file | as file | as file | as file | as file |
| symlink | no | as symlink* | as symlink* | no | no | no | |
| OS X | hard link | as file | as file | as file | |||
| symlink | no | as symlink* | as symlink* | ||||
| Alias | as garbage** | as garbage** | as garbage** | ||||
* The synced symlink might be broken if the file / folder it points to does not exist on destination computer. Also, no files / folders are synced that are pointed by symlink. Only symlink itself.
** This file becomes meaningless and will not therefore open / point to original file after synchronization.