This is on 10.2.6, released Aug 2007.
Issue 7659 was fixed in 10.1.14, released Aug 2005.
You'd think the fix would be in 10.2.6, too, but maybe it has reared
its ugly head again.
My description is not quite the same, but I am on HP. No select
involved. Executing a PORT.STATUS from another session sounds like
something I might have donw. I was examining that program intensely
that afternoon.
Thanks, JayJay! I'll forward this to support.
Chuck
-----Original Message-----
From: John Jenkins
There were some changes to do with PHANTOMS being woken from a SLEEP
when the parent process terminated. It would be interesting to check
your UniVerse release against the Product Availability Matrix:
10.1.14
7659 If one UniVerse process was executing a SELECT statement
against a file, and a different UniVerse process was
executing the PORT.STATUS command, the process selecting
the file may have received an error message similar to
the following:
"nanosleep: Interrupted system call"
This problem was unique to the HP platform and has been fixed.
This might be of help - does it match?
-----Original Message-----
From: Mark Eastwood
I had a similar experience several years ago (10.0.?/Windows).
What I suspect (but never proved) was happening was when I ran
PORT.STATUS, it "touched" the sleeping phantom process and woke it up.
It was of little significance to me, and never encounter on other boxes,
so I never pursued. You should be able to test easy enough.
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
