Tripp Lite B0930042E4U Owners Manual for B093- B097- and B098-Series Console S - Page 216

14. Configuration from the Command Line The config application resides in the /bin directory. The environmental variable PATH contains a route to the /bin directory. This allows a user to simply type config at the command prompt instead of the full path /bin/config. Options -a -run-all Run all registered configurators. This performs every configuration synchronization action pushing all changes to the live system. -h -help Display a brief usage message. -v -verbose Log extra debug information. -d -del=id Remove the given configuration element specified by a '.' separated identifier. -g -get=id Display the value of a configuration element. -p -path=file Specify an alternate configuration file to use. The default file is located at /etc/config/config.xml. -r -run=configurator Run the specified registered configurator. Registered configurators are listed below. -s --set=id=value Change the value of configuration element specified by a '.' separated identifier. -e --export=file Save active configuration to file. -i --import=file Load configuration from file. -t --test-import=file Pretend to load configuration from file. -S --separator=char The pattern to separate fields with, default is '.' -P --password=id Prompt user for a value. Hash the value, and then save. The registered configurators are: alerts auth cascade console dhcp dialin eventlog hosts ipaccess ipconfig nagios power serialconfig services Secondary systemsettings time ups users There are three ways to delete a config element value. The simplest way is use the delete-node script detailed in 15. Advanced Configuration. You can also assign the config element to "", or delete the entire config node using -d: # /bin/config -d 'element name' All passwords are saved in plaintext except the user passwords and system passwords, which are encrypted. Note: The config command does not verify whether the nodes edited/added by the user are valid. As such, any node may be added to the tree. For example, if a user were to run the following command: # /bin/config -s config.fruit.apple=sweet the configurator will not verify, though this command is clearly useless. When the configurators are run to turn the config.xml file into live config, they will simply ignore this node. Administrators must make sure of the spelling when typing config commands. Incorrect spelling for a node will not be flagged. Most configurations made to the XML file will be immediately active. To ensure all configuration changes are active, especially when editing user passwords, run all the configurators: # /bin/config -a For information on backing up and restoring the configuration file, refer to 15. Advanced Configuration. 216