Solaris

I'm running Tibco Hawk (hawkhma and agent) on a number of solaris 10 boxes (both x86 and Sparc).
Tibco Hawk is a monitoring system, that can monitor processs and logs on the OS and applications. It also have the ability to start a process, if it for some reason, have died.

I have implemented hawk as a Solaris SMF service and it runs very well itself, except from one thing:

When Hawk monitors a process on the box, if that process stops for any reason and is restarted by hawk, that new process does now belong to the hawk SMF service as an assosicated process.
This can be verifyed by svcs -p hawk , which list the processes associated with the service.

So far everything appears to be ok. But if, for any reason, I want to stop the hawk service, (by running svcadm disable hawk), all associated processes are stopped, which means both the hawk processes itself, but also the monitored processes are terminated.
Clearly I don't want my monitored processes to stop, just because the monitoring is down temporarely.

So my question:
Is there anyway to avoid the monitored processes gets associated with the hawk service, once they have been started by it ?
Or if the have been associated, can they somehow be excluded or removed from the service ?

any recommendations or suggestions are very welcome

/ulrik

can u provide the output of this command then i will provide the solution


ps -ef | grep -i hawk

radmin@rmds-p2ps1-a# ps -ef | grep -i hawk
root 27923 1797 0 nov 28 ? 78:03 /opt/reuters/SOFTWARE/hawk/bin/tibhawkhma -file /opt/reuters/SOFTWARE/hawk/bin/
radmin 18315 18293 0 13:42:44 pts/10 0:00 grep -i hawk
radmin 28002 1797 0 nov 28 ? 315:05 /usr/java/bin/java -DTIBHawk=agent -Dhawk.hawk_root=/opt/reuters/SOFTWARE/hawk
radmin@rmds-p2ps1-a#