On 23/11/17 15:59, Mike Fleetwood wrote:
Cron starts configured jobs at the scheduled time asynchronously.
I.e. It doesn't block waiting for each command to finish. Cron notices
when the job finishes and any output produced, written to stdout and/or
stderr, by the job is emailed to the user. So no, a 2 hour job is not a
problem for cron.
Minor additional advice -- prepend you command with:
flock --nonblock /var/run/scrub.lock
to avoid running several scrubs simultaneously in case one takes more
than 24 hours to finish.
--
With Best Regards,
Marat Khalili
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
