crontab -r is way too close to crontab -e…
8 comments
@heliomass @paul that’s avoiding an opportunity to test an unplanned restore from backup @paul been there done that… once I even forgot to include any argument after crontab command on Solaris and it replaced existing crontab with empty one @paul I made that exact observation some 20 years ago when I nuked all the cron jobs on our pet email server at school by slipping a tiny amount on the keys @paul hence my alias crontab='crontab -i' in my .bashrc , asks for yes/no when accidentally fucking up |
@paul Oh yes. I have a cron row to periodically dump the crontab to a file for exactly this reason. It’s very meta.