Running dcontrol
Running dcontrol
Section titled “Running dcontrol”There are 2 files required in order to run the dcontrol program: The settings file (in json or yaml format), and the license file (except when using the trial license).
Argument Options
Section titled “Argument Options”You can run dcontrol with the following options:
-
-h, --help
- Display the application help.
-
-v, --version
- Display the application version info.
-
-f, --file <file>
-
The settings file location settings.[yml|json], defaults to /etc/dcontrol/settings.[yml|json].
-
-l, --licensefile <file>
-
The license file location license.json, defaults to /etc/dcontrol/license.json.
-
-t, --test
- The settings file for errors.
-
-V, --verbosity <level>
-
Set the verbosity level of the application.
0- ‘silent’: No verbose output at all.1- ‘critical’: Only output critical messages.2- ‘warning’: Output critical and warning messages (default).3- ‘info’: Also print informational messages.4- ‘debug’: Be very verbose, for debugging purposes only.
-
-T, --no-time-logging
-
Remove the date- & timestamps from the log messages. Useful when launching trough systemd as journald will include its own timestamps.
- --trial
-
Request and use a trial license key. Plugins or products for which no valid license key was found will use a trial license (valid for 30 days)
Subcommands
Section titled “Subcommands”license
Section titled “license”-
license --id
- Show the computer hardware id.
-
license --list
- List all installed licenses.
-
license --release <plugin>...
-
Release the license of one or more plugins. A single or multiple plugins or ‘dcontrol’ itself can be released individually. When given the ‘all’ options all licenses will be released. Releasing a license makes it available for usage on a different system.
plugin
Section titled “plugin”-
plugin --list
- List all installed plugins.