On Tue, 14 Feb 2012, Jason White wrote:
Tim Connors <tconnors@rather.puzzling.org> wrote:
Can we define a new standard is-not-quite-cron?
Systemd developers are planning to support Cron-like scheduling if that helps you.
Yeah, as soon as I pressed "send", I realised I should have clarified: "and not systemd!". I prefer my software without tentacles. http://upstart.ubuntu.com/wiki/ReplaceCron "Cron compatibility A new cron event on cron MINUTE=mm HOUR=hh DOM=dd MONTH=mm DOW=w This allows a script to use normal cron times because of pattern matching" I mean, *why*? Why would you even consider highlighting that as a feature? If you're wanting to plug it into the place of cron, then that format helps no one, because it looks nothing like cron except the ordering of the fields (you also don't edit cron fields through the commandline). Of course things that look like the standard way you set environment variables (<named field>=<value>) doesn't depend on order. There's no need to highlight that as a "feature", especially when the particular feature in question is so crufty. I also don't like my cron replacement being so dependant upon the init replacement[1] and requiring a special bus that isn't allowed to be restarted lest it crash the system (hello DBUS funk!). [1] Anyone else think that parallel boot is so much more pain than it's worth? eg, debian bug #634215 -- Tim Connors