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?
Regtards
JayJay
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mark Eastwood
Sent: 13 February 2008 15:10
To: [email protected]
Subject: RE: [U2] SLEEP 60 slept only 53 seconds, or else TIMEDATE() is
wrong
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.
Mark
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Stevenson,
Charles
Sent: Tuesday, February 12, 2008 4:17 PM
To: [email protected]
Subject: [U2] SLEEP 60 slept only 53 seconds, or else TIMEDATE() is
wrong
I've never seen this before. Can anyone explain it?
I'm testing UV 10.2.6 on HPUX 11.23, Itanium & found this while
debugging a program that runs as a phantom.
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
