On Fri, Aug 24, 2007 at 11:05:08PM -0700, Jon S wrote: > Given the Cluster Suite's preference to disable, restart or relocate a > service after an init script resource returns non-zero, I'm curious how > best to handle a significant number of applications tied to a single > IP resource. The easy thing to do is to just define a bunch of init > scripts in a single service with the IP resource. Problem is, of course, > that if one script returns non-zero, all resources in the service are > stopped and restarted. I never tried defining multiple services in one script, I assume it works as you say. But I prefer another solution: create one service script and in that script call the various init scripts (or start the applications directly, all dependent on the type of application). Still, if your script is asked to "stop" the service, you should stop all apps, as you don't know the reason. The only way to circumvent this is to make the "status" of this all-in-one service script more intelligent: if one application has a problem, it could try to restart that specific application and, if that succeeds, just return 0 as status for the service as if nothing has happened. The other solution is to use different services, but that requires different IP addresses. -- -- Jos Vos <jos@xxxxxx> -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6948204 -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
