feature request - backoff on x number of -n failures

[crustymonkey]

feature request - backoff on x number of -n failures

[crustymonkey]

Yep, 1240 emails are never desired. The problem that cron-wrap solves isn't one of scheduling here, but rather one of notifications. I think it would make a lot of sense to add an option for exponential backoffs, and I can definitely make that happen. That way you wouldn't have the spam problem, which is one of the main things that cron-wrap was written to solve.

yup. exponential would be even better.

[crustymonkey]

I've added a -b option which will exponentially back off the notifications. Grab version 0.6.0 (or clone the latest on master) for the addition.

awesome :-) thanks !

I'm using /usr/bin/cwrap.py -b -n 5 -t 30 but i'm now getting emails for every fail (one per minute).

I'm guessing one of -n, -b, or -t has cancelled the effect of the others out.

[crustymonkey]

That's odd. I tested pretty much every combination I could for that. I'll take a look and reopen this.

[crustymonkey]

I figured this one out. There was a new instance variable added to the state instance, which gets serialized and saved to disk to save state between runs. Well, since it's saving an already instantiated instance to disk, when it unserializes it, it doesn't call init() and initialize the new variable. Therefore, it would throw a python error every time it runs trying to access a variable that didn't exist.

I added an upgrade method that can handle these for this case, and in the future.

You can also delete the old state files to fix this, but the 0.6.1 version should just handle the upgrade automatically now.