Introducing Chronos: A Replacement for Cron

Post by thezilch » Sun, Mar 17, 2013, 6:03 AM UTC

kelnos wrote: post #60

thezilch wrote: post #39

Earlier quoted context omitted.

You will get said timer support in Redis 2.8 with the ability to subscribe to keyspace events, which includes keys expiring (with millisecond resolution). https://github.com/antirez/redis/issues/594 psubscribe __keyevent@0__:expired cron_* psetex cron_run-me-in-1s 1000 0

It's not clear to me from the writeup if you'll get notification when the key actually expires, or when the key is expired because someone tried to access it. Currently keys don't actually really expire from the datastore until someone tries to access it after its TTL runs out. Changing redis so it will actually actively expire keys at the precise time the TTL runs down sounds expensive... but I would love that featu…

Post by zobzu » Mon, Mar 18, 2013, 5:32 PM UTC

bitwize wrote: post #23

zobzu wrote: post #19

so... cron's a 200kb self contained C program, super simple, does one thing, and does it well. Chronos is built on top of frameworks, needs a few services to run. Certainly it has value, but marketing it as a cron replacement is wrong imo. Chronos is one of these "web-server-service-tool" thingie, but no, it's not cron.

Every time I come across one of these heavyweight, dependency-encrusted "replacements" for basic Unix tools, I'm reminded of L33tStart[0], a fictional, satirical init(1) replacement I wrote about on Reddit -- a sort of parody of systemd. Every day, in a bizarre manifestation of Poe's Law, L33tStart seems less and less a parody. [0] http://www.reddit.com/r/programming/comments/14ay0r/hacker_k...