davidmarsh, 5 months ago

@paul been there

thickey, 7 months ago

@paul I’m sure it made total sense to the developer of cron way back when. But it’s a little disaster waiting to happen on every server.

sbattey, 7 months ago

@paul yes. That happened to me like 3 months ago. I was displeased.

dakira, 7 months ago

@paul oh man, when this happened to me, I actually tried to find out who‘s responsible for this mess.

sriehl, 7 months ago

@paul Welp, I have a new fear now

jpdeckers, 7 months ago

@paul hence my alias crontab='crontab -i' in my .bashrc , asks for yes/no when accidentally fucking up

stormhair, 7 months ago

@paul totally agree, I’ve been bitten by that one too

hejsna, 7 months ago

@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

bnoon, 7 months ago

@paul Yep, did that when typing in a shell on my phone. I just stared at the returned prompt in disbelief. Had to go to the man page to see what -r did.

amethyst, 7 months ago

@paul you could always switch to Dvorak 🤪

enkydu, 7 months ago

@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

Baby Facepalm GIF by MOODMAN

heliomass, 7 months ago

@paul Oh yes. I have a cron row to periodically dump the crontab to a file for exactly this reason. It’s very meta.