| 355 | | For the time being, we should test the workings of the script. A crontab has been added on ippc30 which runs the script every 3 hours and pipes the output of the check_diffs for both gpc1 and gpc2 to the ps-ipp-ops mailing list. Furthermore, for the czars, they should try out desperate diff queuing using the new way by picking an appropriate desdiffdt time when the first chunk is done and incomplete. A word of caution: '''Do not use a desdiffdt that is too short!''' The timescale is there by virtue of not having a more sensible way of judging whether a chunk is complete and will not be resumed/picked up. Picking a very low desdiffdt could lead to unforeseen circumstanced like queuing desperate diffs for chunks still in progress or temporarily interrupted. |
| | 355 | For the time being, we should test the workings of the script. A crontab has been added on ippc30 which runs the script every 3 hours and pipes the output of the check_diffs for both gpc1 and gpc2 to the ps-ipp-ops mailing list. Furthermore, for the czars, they should try out desperate diff queuing using the new way by picking an appropriate desdiffdt time when the first chunk is done and incomplete. A word of caution: '''Do not use a desdiffdt that is too short! ''' The timescale is there by virtue of not having a more sensible way of judging whether a chunk is complete and will not be resumed/picked up. Picking a very low desdiffdt could lead to unforeseen circumstanced like queuing desperate diffs for chunks still in progress or temporarily interrupted. |
| | 356 | |
| | 357 | The script will not execute diffs when using the debug option, so we can check its usage and behaviour. The messages regarding the new subroutine are marked using outputs preceded by the header desp_diff_singles: |
