News for hackers. Stuff that matters.
Re:Ask HN: What simple tools or products are you most proud ... by josho on Tuesday November 15, 2016 @11:14AM (#12959262)
As someone about to write a cron job, what ways do you see Cron fail?

My assumption is that cron is robust and reliable, it's the job script itself that may fail silently and need monitoring, yes?

Re:Ask HN: What simple tools or products are you most proud ... by augustflanagan on Tuesday November 15, 2016 @11:46AM (#12959669)
Yeah, I'd say your assumption is correct. However, other common ways that I've seen cron "fail" is for the cron entry to being installed in the wrong user's crontab, the permissions on a script changing such that it can't be executed, temporarily disabling or removing a cron job and forgetting to re-enable it, etc.
Re:Ask HN: What simple tools or products are you most proud ... by Procrastes on Tuesday November 15, 2016 @05:29PM (#12962920)
My favorite is forgetting a newline at the end of the crontab. I always put a warning at the bottom of my crontabs.

# Always end with a newline!

Re:Ask HN: What simple tools or products are you most proud ... by SteveNuts on Tuesday November 15, 2016 @01:44PM (#12960934)
The most common failure I've seen is when people forget to use full paths in cron.

bash instead of /bin/bash (or similar)

Re:Ask HN: What simple tools or products are you most proud ... by wagmo on Tuesday November 15, 2016 @08:11PM (#12963782)
There's other weirdness in cron-land too. Cron will completely ignore files containing "." .
Re:Ask HN: What simple tools or products are you most proud ... by yogeshnachnani on Wednesday November 16, 2016 @07:07AM (#12966276)
The cron process can be killed by the oom_killer, resulting in missed crons. This may be aggrevated If the cron service is never respawned later.