News for hackers. Stuff that matters.
Re:Motherfriggin' Cron by PeterWhittaker on Thursday May 29, 2014 @11:03PM (#7820010)
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.

Re:Motherfriggin' Cron by notduncansmith on Thursday May 29, 2014 @11:27PM (#7820094)
Well, 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!

Re:Motherfriggin' Cron by PeterWhittaker on Friday May 30, 2014 @08:28AM (#7821363)
Well, 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

Re:Motherfriggin' Cron by bediger4000 on Thursday May 29, 2014 @11:22PM (#7820081)
I understand your viewpoint, but unless those whippeer snappers make the mistakes, they'll never learn.
Re:Motherfriggin' Cron by alex_doom on Friday May 30, 2014 @12:25AM (#7820267)
But without grumpy elders, we'll never know we fuck up! Chicken > Egg < Chicken?
Re:Motherfriggin' Cron by PeterWhittaker on Friday May 30, 2014 @08:30AM (#7821370)
And 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.