A utility to control the dominator.
The domtool utility may be used to control a running dominator. Domtool may be run on any machine and can be used to manipulate various operating parameters of a running dominator and perform RPC requests. It is typically run on a desktop or bastion machine.
Domtool supports several sub-commands. There are many command-line flags which
provide parameters for these sub-commands. The most commonly used parameter is
-domHostname which specifies which host the dominator to control is running
The basic usage pattern is:
domtool [flags...] command [args...]
Built-in help is available with the command:
Some of the sub-commands available are:
- configure-subs: set the current configuration of all subs (such as rate limits for scanning the file-system and fetching objects)
- disable-updates reason: tell dominator to not perform automatic updates of subs. The given reason must be provided and is logged
- enable-updates reason: tell dominator to perform automatic updates of subs. The given reason must be provided and is logged
- get-subs-configuration: get the current configuration that is pushed to all subs
Dominator restricts RPC access using TLS client
authentication. Domtool will load certificate and key files from the
~/.ssl directory. Domtool will present these certificates to dominator. If
one of the certificates is signed by a certificate authority that dominator
trusts, dominator will grant access.
The most important sub-commands are described below for convenience.
To disable automated updates, issue the following command:
domtool -domHostname=mydom.zone disable-updates "my stop reason"
This will prevent the dominator running on the host
mydom.zone from performing automated updates. The reason for the emergency
stop along with the username of the person issuing the stop is logged.
To enable automated updates, issue the following command:
domtool -domHostname=mydom.zone enable-updates "my restart reason"
This will restart automated updates. The reason for the restart (typically an explanation of why the emergency stop is no longer needed) along with the username of the person issuing the restart is logged.
There is no documentation for this package.