Assuming that the znapzend (script) calls a system program in a loop, and that program returns well or dies, the script should handle it somehow, e.g. go to the next iteration of the loop, or abort with error and cause service restart. Either way, for the hands-off end-user, the clock goes on ticking and snaps taken.
Coverage remained the same at 85.901% when pulling ab776dddacf8ba5a6829bec6e09a79056c96abd4 on jimklimov:nocore into d1161bfb7febcd9f4d49deac42d5f3289c271576 on oetiker:master.
Coverage remained the same at 85.901% when pulling ab776dddacf8ba5a6829bec6e09a79056c96abd4 on jimklimov:nocore into d1161bfb7febcd9f4d49deac42d5f3289c271576 on oetiker:master.
Coverage remained the same at 85.901% when pulling ab776dddacf8ba5a6829bec6e09a79056c96abd4 on jimklimov:nocore into d1161bfb7febcd9f4d49deac42d5f3289c271576 on oetiker:master.
Coverage remained the same at 85.901% when pulling ab776dddacf8ba5a6829bec6e09a79056c96abd4 on jimklimov:nocore into d1161bfb7febcd9f4d49deac42d5f3289c271576 on oetiker:master.
Assuming that the
znapzend
(script) calls a system program in a loop, and that program returns well or dies, the script should handle it somehow, e.g. go to the next iteration of the loop, or abort with error and cause service restart. Either way, for the hands-off end-user, the clock goes on ticking and snaps taken.