|Using the Aspera Watch Service and WatchFolders|
When used in conjunction with ascp commands, the Aspera Watch Service allows for fast detection and send of new and deleted items. By comparing snapshots of the file directory it is watching, asperawatchd generates file lists for ascp commands for transfers and delete requests.
To enable asperawatchd, follow these steps:
<server> <watchd> <enabled>true</enabled> <log_level>log</log_level> <log_directory>/tmp</log_directory> <max_directories>1000000</max_directories> <max_queue>100000</max_queue> <max_snapshots>10000</max_snapshots> <db_spec>redis:localhost:31415</db_spec> <scan_period>30m</scan_period> <snapshot_min_changes>1</snapshot_min_changes> <snapshot_min_interval>10s<snapshot_min_interval> <watches> <watch> <path>/data/D1</path> </watch> </watches> </watchd> </server>
The <watch> section specifies directories for asperawatchd to monitor. When starting a session with Aspera Sync, Sync requests snapshots from asperawatchd, a process which takes longer depending on the number of files in the directory. The asperawatchd service periodically scans the directories specified in aspera.conf, reducing time spent waiting for a new completed scan. You can set values for <snapshot_min_changes> and <snapshot_min_interval>, which cause asperawatchd to reject the creation of snapshots if not enough changes have occurred in the watched directories or if not enough time has passed since the last snapshot.
# service asperawatchd startCheck to make sure the asperawatchd service is running.
# ps aux | grep watchd root 2306 0.1 0.5 732968 11220 ? Ssl Nov13 1:17 /opt/aspera/sbin/asperawatchd