I am using QNET quite a lot, and it is working quite well BTW. I like the
features it has over QNX 4 Fleet. Especially being able to use names
instead of numbers. This is working out very well.
Just a few tid bits that are a bit anoying and troublesome. Today I was
doing a lot of starting various resource managers across the net using both
on-f and on -n , and it works great…but every once and a while, “on” would
not go away (get stuck in a “NET_REPLY” state and thus I wouldn’t get the
shell prompt back after a remotely spawned program would try to exit.
I looked later at my list of processes and saw a large number of ‘on’ just
hanging around, unable to exit as there were all in this "NET_REPLY state.
I tried killing io-net and then restart it, but alas, that operation froze
the system. I didn’t have a high poriority shell running so I couldn’t do
any repairs and had to reboot.
I’m worried about mainly one thing…if I have a process doing IPC it looks
like it is possible for the other end to reply and the process being replied
to to not get the message and continue to wait. Additionally…there
doesn’t seem to be a way to kill it (seems to be hung on io-net?). What can
I do to guarantee that my processes won’t get stuck in this state?