| 129 | | The 'all' option 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 {{{edit}}} option can be used when creating a config for the first time, or to edit an existing one. |
| | 129 | The 'all' option 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 {{{edit}}} option can be used when creating a config for the first time, or to edit an existing one. As an example: |
| | 130 | |
| | 131 | {{{ |
| | 132 | ./run.sh queue.py edit |
| | 133 | * Name for new config, or existing config to edit? testconfig |
| | 134 | * datastore_product (varchar(30))? PSPS_test |
| | 135 | * datastore_type (varchar(30)) hit return to accept default of: 'IPP_PSPS'? |
| | 136 | * datastore_publish (tinyint(1)) hit return to accept default of: '0'? 1 |
| | 137 | * dvo_label (varchar(100))? MD04.20120307 |
| | 138 | * dvo_location (varchar(1000))? /data/ipp005.0/gpc1/catdirs/LAP.ThreePi.20110809 |
| | 139 | * min_ra (double) hit return to accept default of: '0'? |
| | 140 | }}} |