Changes between Version 17 and Version 18 of ValidationIntro

Timestamp:

May 30, 2014, 8:03:11 AM (10 years ago)

Author:

Christian Beer

Comment:

updated to reflect current code

ValidationIntro

@@ -43 +43 @@
 A validator (either standard or custom) has the following command-line arguments:
 
- --app appname::        Name of the application
- [ --one_pass_N_WU N ]::        Validate at most N WUs, then exit
- [ --one_pass ]::       Make one pass through WU table, then exit
- [ --mod n i ]::        Process only WUs with (id mod n) == i. This option lets you run multiple instances of the validator for increased performance.
- [ --max_granted_credit X ]::   Grant no more than this amount of credit to a job.
- [ --update_credited_job ]:: For each valid result, create an entry in the credited_job database table.
+ --app appname::              Name of the application
+ [ -d N ]::                   Sets the log verbosity level. 1=low ... 4=high.
+ [ --sleep_interval n ]::     Sleep n secs if there was nothing to do within the last pass
+ [ --one_pass_N_WU N ]::      Validate at most N WUs, then exit
+ [ --one_pass ]::             Make one pass through WU table, then exit
+ [ --dry_run ]::              Don't update db, just write logs (for debugging)
+ [ --mod n i ]::              Process only WUs with (id mod n) == i. This option lets you run multiple instances of the validator for increased performance.
+ [ --max_wu_id n ]::          Process only WUs with id <= n
+ [ --min_wu_id n ]::          Process only WUs with id >= n
+ [ --max_granted_credit X ]:: Grant no more than this amount of credit to a job.
+ [ --update_credited_job ]::  For each valid result, create an entry in the credited_job database table.
   This lets you keep track of which user contributed to each WU, even if you use [DbPurge db_purge].