crontabin the late 1990s, and I still run many of those same crontabs. I mean, same program, same times. So, my understanding of that tool is very tied to that time.
Of course, very little changes in technology over 15 years. </sarcasm> So I recently looked through
man 5 crontaband found that there are special strings for certain common times.
| ||Run once, at startup.|
| ||Run once a year, "0 0 1 1 *".|
| ||(same as @yearly)|
| ||Run once a month, "0 0 1 * *".|
| ||Run once a week, "0 0 * * 0".|
| ||Run once a day, "0 0 * * *".|
| ||(same as @daily)|
| ||Run once an hour, "0 * * * *".|
Some of these come with variable utility. What are you doing on a system that's
@yearly? Sending "Happy New Year!" to everybody you know? There's much here that strikes me as better done connecting to a calendar. In fact, I'm hatching an idea of setting up a calendar in Google Calendar to do that sort of wide-ranging crontabby or batchy stuff. If something runs less common than weekly, it doesn't get into my crontabs.
I'm really drawn to the
@rebootstring. For my work setup, I have FUSE mounts to a great number of machines (which I really use) and a specific line to configure the line-in to go directly to line-out so I can route my Windows box and Android phone through my Linux box to my headphones. I've put those commands into my crontab at