In its Peer Mode, SyncDat will look for any changes which have occurred since the last scan of the remote directory. It will then attempt to propagate the changes it finds, subject to access permissions. This mode may be used when changes have been made to files on both sides.
Peer Mode is especially sensitive to system clock accuracy, change conflicts, and disruptions. Mismatched system clocks, changing the same file on both sides, or a system disruption may cause incorrect operation and loss of data.
Peer Mode is not recommended wen running SyncDat in a scripted, automated, or otherwise unattended environment.
First specify the pathname to the local directory. Then specify the DNS name or IP address of the remote server, followed by a colon (:), and the remote pathname. If the server requires a username, include that in front of the server name, separated by an at-sign (@). See the Authentication section for more details about specifying credentials.
syncdat -P localpath firstname.lastname@example.org:remotepath
You may omit the "remotepath" if you are synchronizing to the remote home directory. You may omit the "username" if Anonymous Users has been enabled on the server. For example:
syncdat localpath example.com:
If a file exists on only one side and is newer than the last scan time, it will be copied to the other side.
If a file exists on only one side and is older than the last scan time, it will be deleted unless the NoDelete option is set.
If a file exists on both sides, one copy is older than the last scan time, and one copy is newer, then the newer copy will overwrite the older one.
If a file exists on both sides and both copies have been modified since the last scan time, then the files will be considered conflicting. If the "Yes" option has been selected, the newer file will overwrite the older one. Otherwise, if the "Quiet" option has been selected or the terminal is not-interactive, the files will be ignored. By default, if the terminal is interactive, the user will be asked how to resolve the conflict.
See User Queries for a list of potential conflicts and the actions taken when running without user interaction.