Bear this in mind when scheduling checks. The checker will keep starting new bitstream checks for the specific durations, so actual execution duration will be slightly longer than the specified duration. You may use any of the time arguments below: Example: [dspace/bin/dspace checker -d 2h(Checker will run for 2 hours) The Checksum Checker's default execution mode is to check a single bitstream, as if the option was -c 1ĭuration mode: /bin/dspace checker -d To run the Check for a specific period of time with a time argument. Example: [dspace/bin/dspace checker -c 10 This is particularly useful for checking that the checker is executing properly. The -c option if followed by an integer, the number of bitstreams to check. Limited-count mode: /bin/dspace checker -c To check a specific number of bitstreams.(Note that this means that the most recently ingested bitstreams will be the last ones checked by the Checksum Checker.) ![]() Unless a particular bitstream or handle is specified, the Checksum Checker will always check bitstreams in order of the least recently checked bitstream. Information on the options are found in the previous table above. Configuration for specific configuration beys in the dspace.cfg file.Įxecution mode can be configured using command line options. ![]() the policy for removing old checksum results from the database The user should refer to Chapter 5.There are three aspects of the Checksum Checker's operation that can be configured: Prune old results (optionally using specified properties file for configuration
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |