Rodney Lott <email@example.com> wrote:
I would like to know if there is a way to identify all of the processes that
are attached to a particular Phindows session. To elaborate, let’s suppose
I have a Phindows session open and I have a couple of pterms open, some with
vim running in them, as well as PhAB, and the helpviewer. Now, for some
reason, I leave for a while and I come back. Phindows then dies on me with
some unknown Windows memory error. If I wanted to go back into the node
that I was working on and clean up all of the resources that are still
running and were not cleaned up, how would I be able to identify the
children of the crashed Phindows session?
I am not an expert in Photon/Phindows, but I think that each Phindows
session will have its own Photon server, and all Photon applications
should have a fd open to that Photon’s name special device. (The
default example, would be “/dev/photon”.)
So, doing a “sin fd” would give you something like:
And, I think the different Photon sessions would have different names
for there /dev/photon files – I would try taking a look at what this
gives you in the normal case, and see if you can start to figure things
out from that.
I think, also, Photon takes a -N name to give it which name to
register, you might be able to use this to figure out which clients
are associated with which Photon session, if you’re hosting multiple
Phindows/Photon sessions on the same machine. “sin arg” will give
you the command line arguments for running processes.
Hope this helps,
As well, does anyone know if there is an issue with screensavers in Windows
and Phindows. This crashing that I have described seems to happen whenever
I go away for a while and then come back to my machine whereupon the
screensaver is active.
Nope, sorry, no experience with that.
QNX Training Services
Please followup in this newsgroup if you have further questions.