Live data from Hacker News

Get notified when a periodic task doesn't run

51–52 of 52 posts

Re: Get notified when a periodic task doesn't run

#51

Post by cheap » Tue, Sep 25, 2012, 5:02 PM UTC

gm wrote: post #34

cheap wrote: post #24

Earlier quoted context omitted.

If I charged my clients $19.99 a month for something like this they'd laugh at me and hire someone else.

Then you have the clients no one else wants (maybe that's why you have that username?). You can keep them. Smart people go after customers willing to pay more. Actually, I have some old cheap clients I fired some time ago... Should I send them your way? They need someone to yell at and then laugh at when the cost of their needs are quoted.

You are totally right, my clients do want to pay more for this kind of thing. BTW, your penis is huge.

Re: Get notified when a periodic task doesn't run

#52

Post by Nick_C » Wed, Sep 26, 2012, 5:08 AM UTC

Those using cron hacks to check on previous cron jobs might want to take a look at Matt Dillon's cron (as opposed to Paul Vixie's cron), which is the crond that Slackware uses.

It has named cron jobs, @noauto and AFTER keywords, which let you run jobs depending on whether previous jobs (identified by name) have run successfully.

That, combined with using things like && and || and mailx, give you quite powerful ways of checking on previous cron jobs.

Post reply on HN