Thanks for your fast advice. Unfortunetly problem is a liitle bit complicated and now I try to describe it. I try to spawn resource manager form node 1 to node 2. so I call:
but then I want to return to prevoius location to make some ather job on the first node (for example to connect to this resource manager and make some locall spawn). Callling
is intiuitive but it doesnt work because after second:
resource manager doesn’t start fine. The symptom is that path become longer and longer. I can’t change it in 6.3.0.
I found solution in 6.2.1
chroot("…/…/…/…/…/…/…/"); //or longer
it looks terrible but it worked. I could call this section again and again and everything worked fine. Unfortunetly in 6.3.0 it stoped. The way spawn behave seems to be enormous QNX bug, or I am wrong ?? Maybe someone from QNX devolopers will think about it and fix it. After dooing great job with gns mechanism in 6.2.1 to 6.3.0 migration, this is maybe the last major qnet bug left.
Please let me know if there is other technique of making multiple network spawn in code of one process. I started to thing about cascade spawn to spawn locally and then globally (quite complicated) or using "on -f …’ but what about pid of child then ??