Setting Custom Watch Scan Periods

When a new watch is created, it uses the default scan period set in aspera.conf unless otherwise specified. You can update the aspera.conf setting, in which case all watches created after the update use the new scan period but existing watches are not updated. You can also update the scan period of an existing watch.

Update the Default Scan Period

To update the default scan period, run the following command:

> asconfigurator -x "set_server_data;watchd_scan_period,value"
To activate your change, restart the Watch daemon by running the following command:
> asrun send --disable service_id
> asrun send --enable service_id

Retrieve the service ID by locating the ID of the service with "type": "WATCHD" in the output of the following command:

> asrun send -g

Update the Scan Period of an Existing Watch

To update the scan period of an existing watch, run the following command:

> aswatchadmin update-watch daemon watch_id --scan-period=seconds
To activate your change, restart the Watch daemon by running the following command:
> asrun send --disable service_id
> asrun send --enable service_id

Retrieve the watch ID by running the following command:

> aswatchadmin query-watches daemon -c