I have two related questions. The first is how can a daemon supplying a service indicate that there is a problem and that the service should go into maintenance rather than having the restarter restart it?
Secondly, on a related note, is there anyway to mark a service as "not applicable"? If, for instance a service that was designed specifically for a particular configuration found itself started on a system without that configuration, is there a way for the daemon to exit and not get restarted and not appear in maintenance but still get started on the next reboot? -- blu "Remember 'A Thousand Points of Light'? With a network, we now have a thousand points of failure." ---------------------------------------------------------------------- Brian Utterback - Solaris RPE, Sun Microsystems, Inc. Ph:877-259-7345, Em:brian.utterback-at-ess-you-enn-dot-kom
