Changes between Version 275 and Version 276 of ippToPsps

Timestamp:

Apr 5, 2012, 3:19:42 PM (14 years ago)

Author:

rhenders

Comment:

--

ippToPsps

@@ -143 +143 @@
 {{{
 cd trunk/ippToPsps/jython
-./run.sh prog.py someConfigName
+./run.sh prog.py someConfig
 }}}
 
@@ -150 +150 @@
 All {{{ippToPsps}}} programs register with the {{{ippToPsps}}} database upon start-up, adding a row in the [wiki:ippToPsps_Database#Theclientstable clients table]. While running, all programs routinely check the {{{ippToPsps}}} database to check for changes in the config, or to see if they should be paused or stopped.
 
-The config argument can be the name of any config in the [wiki:ippToPsps_Database#Theconfigtable config table of the database] or it can be 'all'. This will mean that the program in question will cycle through all 'active' configs. This is handy for programs like {{{metrics.py}}} or {{{cleanup.py}}}; instead of having an intance of these programs per config, one instance can cycle through them all.
+The config argument can be the name of any config in the [wiki:ippToPsps_Database#Theconfigtable config table of the database] or it can be '''{{{all}}}''', or it can be '''{{{edit}}}'''. Using {{{all}}} will mean that the program in question will cycle through all 'active' configs. This is handy for programs like {{{metrics.py}}} or {{{cleanup.py}}}; instead of having an intance of these programs per config, one instance can cycle through them all. Using {{{edit}}} first prompts the user for a config name. If the name of an existing config is given, then the user can them edit the current settings. If a new name is provided then the user is prompted for all necessary fields to build-up that new config.
 
 All programs catch Ctrl-C for clean exiting, and all programs write a log to stdout and some to file, the location of which is set in the [browser:trunk/ippToPsps/config/settings.xml settings file].