Hello again,

I'm creating a manifest for service application/A that starts some 
master daemon and this daemon later starts some other processes which 
start yet another processes. My current problem is that when master 
daemon is killed it's not restarted due to other running processes in 
the contract. So I'd like to decouple the master daemon and the other 
processes. These other processes are the same except for the arguments 
they have, so I  could introduce a service application/B that would 
depends on application/A and would contain all the other processes. But 
I don't see a way how to do that, since normally the processes are 
started by the master daemon. I would like the most if I could have just 
one instance of application/B and somehow say start this process as part 
of service B. Is there a way (libscf does not help me much)?

Other solution for me would be if I could say only the processes when 
SMF start method exited should be part of the contract. If such process 
spawns another process, SMF would ignore it, as I don't really care 
about it. But I suppose there's no such thing right?

Is this solvable without rewriting master daemon logic much?

Many thanks,
    Lubos.

Reply via email to