>Give me a few minutes to recover from laughing, please. Impenetrable. Lololololol. ? It's a personal opinion, you can laugh all you want but that won't make i

>Give me a few minutes to recover from laughing, please. Impenetrable. Lololololol. ? It's a personal opinion, you can laugh all you want but that won't make it any more wrong than yours. >Those just feel out of scope to me. Why would I want this tool to handle that? I run my backups with a systemd timer. Since it's a desktop system it might not be online during a desired timeslot so the backup can be repeated once the machine becomes available after that. Additionally it prevents concurrent backup runs on my servers if a snapshot is taking longer for a reason (which does happen when too many servers get scheduled at the same time, which btw, is handled by having the timer with a random offset to the schedule which last I checked is not present in cron). It's something I want this tool to handle, yes. >So much laughing this morning! You should really try an open mic night! Why? Because I find a tool that solves my problems useful? Sounds like you should reconsider your standpoint because to me it sounds like you claim that cron is the one true tool to solve timed scheduling of scripts. Which it clearly isn't since cron doesn't solve the problems I have.