A thing I'm noticing about legacy scripts is that if the dates in the names collide, they hang, waiting for a response to "overwrite?" - as much as possible we need to avoid this in automatically triggered scripts, and solving the problem once is part of the benefit of Bibliotech
Strategies:
Where possible, run subordinate programs in "batch" or "non-interactive" mode
Judicious use of "yes"
Spot solutions - e.g. check to see if there's an existing gz file before running gz.
A thing I'm noticing about legacy scripts is that if the dates in the names collide, they hang, waiting for a response to "overwrite?" - as much as possible we need to avoid this in automatically triggered scripts, and solving the problem once is part of the benefit of Bibliotech
Strategies:
Where possible, run subordinate programs in "batch" or "non-interactive" mode
Judicious use of "yes"
Spot solutions - e.g. check to see if there's an existing gz file before running gz.