asperawatchd Configuration

The asperwatchd settings can be configured by using the asconfigurator tool from the command line or by editing the server section of aspera.conf. With these settings you can manage the snapshot database, snapshot frequency, and logging.

To view current asperawatchd settings, run the following command:

# /opt/aspera/bin/asuserdata -a

Configure from the Command Line:

To configure asperawatchd by using asconfigurator commands, use this general syntax:

# /opt/aspera/bin/asconfigurator -x "set_server_data;option,value"

Options and values are described in the following table.

Configure in aspera.conf:

To edit aspera.conf, open it in a text editor with administrative privileges.

/opt/aspera/etc/aspera.conf

For an example of the asperawatchd configuration in aspera.conf, see the sample that follows the table of options and values. Validate aspera.conf after any manual edits by running the following command:

# /opt/aspera/bin/asuserdata -v

asperawatchd Configuration Options

asconfigurator option aspera.conf setting	Description	Default
watchd_max_directories <max_directories>	The maximum number of directories that can be watched (combined across all watches). This setting is used only on Linux machines to overwrite the system value /proc/sys/fs/inotify/max_user_watches. To overwrite the system value with the aspera.conf value, run the setup procedure in the admin tool: # aswatchadmin setup	1000000
watchd_max_snapshots <max_snapshots>	The number of snapshots that are stored in the database before the oldest are overwritten.	10000
watchd_snapshot_min_interval <snapshot_min_interval>	The maximum amount of time between snapshots. If this period passes without the minimum number of changes to trigger a snapshot, a new snapshot is taken.	3s
watchd_snapshot_min_changes <snapshot_min_changes>	The minimum number of changes that trigger a snapshot. If this number is reached before the snapshot minimum interval passes, a new snapshot is taken.	100
watchd_log_dir <log_dir>	Specify the log directory.	The Aspera logging file
watchd_log_level <log_level>	Set the log level.	`log`
watchd_db_spec <db_spec>	Define how the local machine connects to the Redis database.	`redis:127.0.0.1:31415:domain`
watchd_scan_period <scan_period>	The amount of time between asperawatchd assessments of the watches (from end of one to start of the next). asperawatchd assesses watches for change independent of the snapshot minimum interval and snapshot minimum changes to ensure that changes are captured.	30m

Example WatchD Configuration in aspera.conf

...
<server>
    <watchd>
        <max_directories>1000000</max_directories>
        <max_snapshots>10000</max_snapshots>
        <snapshot_min_interval>3s</snapshot_min_interval>
        <snapshot_min_changes>100</snapshot_min_changes>
        <log_dir></log_dir>
        <log_level>log</log_level>
        <db_spec>redis:host:31415:domain</db_spec>
        <scan_period>30m</scan_period>
    </watchd>
</server>