4 ms·
You used a partial path in cron? Wha...? Always, always use fully qualified filenames in cron, never rely on environment variables, ever. And what are you doi
by PeterWhittaker 12y ago
You used a partial path in cron? Wha...?
Always, always use fully qualified filenames in cron, never rely on environment variables, ever.
And what are you doing editing your crontab directly?
% crontab -l > file
% vi file
% crontab < file
That's the proper incantation. Let the tool do what it is supposed to do.
Whipper snappers.
- bediger4000 12y agoI understand your viewpoint, but unless those whippeer snappers make the mistakes, they'll never learn.
- alex_doom 12y agoBut without grumpy elders, we'll never know we fuck up! Chicken > Egg < Chicken?
- notduncansmith 12y agoWell, I've never had someone looking over my shoulder to tell me I was doing it wrong :) As for using partial paths, I was using something that I expected to be in the $PATH, and had no real reason to believe that it wouldn't be there. I definitely learned my lesson with that one. Thanks for the tip!
- PeterWhittaker 12y agoWell, poop. I keep forgetting that HN likes to join lines. % crontab -l > file % vi file % crontab < file is what that should have looked like. #oldman #therewasnomarkupbackthen #mylawnisdead
- PeterWhittaker 12y agoAnd while we're at it: Always make sure your crontab-to-be file ends with an empty line. I tripped over that many, many times before it burned itself into my brain.