| |||||||||||||
|
| |||||||||||||
Poettering: Rethinking PID 1Poettering: Rethinking PID 1Posted May 6, 2010 21:32 UTC (Thu) by mezcalero (guest, #45103)In reply to: Poettering: Rethinking PID 1 by hppnq Parent article: Poettering: Rethinking PID 1
Sorry that I have to disappoint you, but no, most cronjobs don't properly check for concurrent execution.
And the problem of runaway jobs is orthogonal to this, as it applies to every job you run in the system. And we already provide the right tools to deal with this (i.e. timeouts, yadda yadda)
(Log in to post comments)
Poettering: Rethinking PID 1 Posted May 7, 2010 17:47 UTC (Fri) by hppnq (subscriber, #14462) [Link] Bit confused here. I think you would agree with me that for cronjobs where it matters that 1) they run at the scheduled time and 2) there is only one running instance, some amount of intelligence in the job itself is what is needed?
|
|
||||||||||||