"Visser, Martin" <[EMAIL PROTECTED]> writes: Hello Martin,
> * Create / schedule / start /stop / change running processes > * Monitor the status of those processes > * Have the processes alert me when certain milestones occur > * Have the remote boxes exchange heartbeat with the central server (so that they > know they "out of control" and need to abort any runnning jobs) I think cfengine covers most of the requirements, if not all. It's very powerful, but its power comes at a cost :) every time I've looked at it, I got bored and moved on, but I would imagine it would be less work than rolling your own. Another bit of software I'm interested in, which you might find useful for managine alarms is eemu - enterprise Event Management Utility. The last time I looked, there is a small functional open source perl program, but the bells and whistle version is proprietary. But the model is really nice, and scales better that SNMP polling. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
