Enabling "Self Healing" on Foundry

[rarified]

The time has come to put all the background services under the gentle hand of a service monitor. To maximize the impact (not really!) I've picked the Crowd authentication system as the first volunteer. Nothing like a little pressure to motivate one to do it right the first time

This should have no visibility to users of Foundry services. Really. But if something went wrong in how I set it up, Crowd could be flapping on and off, and I need to hear about it (things like you're trying to use a tool hangs or says you can't be authenticated/authorized when you should.)

What's the difference then and now? If the service monitor notices that Crowd crashes or becomes unresponsive, it will shut down the old Crowd and start a new one, and then restart everything that depends upon it (if needed). So your friendly (voluntary) foundry master doesn't have to check things quite as often as he has been.

_R