On Wed, 5 Dec 2012, Edward Ned Harvey (lopser) wrote:
From: [email protected] [mailto:[email protected]]
On Behalf Of Paul Graydon
One of the things I'm particularly wanting to change in our environment
is how cron processes are handled.
I don't know if this was clear to other people, but to me it wasn't clear...
If you could describe the ideal holy grail of task scheduling that you wish to
find, how would you describe it?
not the original poster, but I think the problem is
cron functionality with the following enhaancements
1. central administration, able to run tasks on any machine (as any user)
2. high availability with duplicate supression. All jobs will run, even if some
machines are down, but a job will not be run more than once.
3. (advanced) ability to execute jobs on one machine only after specific other
jobs (potentially on other machines) have finished.
David Lang
_______________________________________________
Tech mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
http://lopsa.org/
