I do remember that port.status on an older version of UV would reset the idle time of all the unix processes, I haven't checked that recently in current version UV 10.0.2 (our current, not THE current level).
Possibly, whatever is causing the idle to reset, is also breaking the FIFO connection of your blocking wait? George > -----Original Message----- > From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users- > boun...@listserver.u2ug.org] On Behalf Of Dan McGrath > Sent: Monday, December 07, 2009 11:11 PM > To: U2 Users List > Subject: Re: [U2] PORT.STATUS affecting program > > Thanks Wally! > > According to our IT policy, we are not actually allowed to divulge any > details on what software versions, etc, we are using. That's why I > simply posted a message asking if anyone knew anything offhand. > > Being relatively new to the U2 style of through ISV support, when > issues > are detected with previous releases (then fixed), are they only > available through the readme's of later releases or are notifications > passed down through the food chain? Obviously having to wait for and > then scan the readme's of each new release is a slow of tedious method > of finding out about potential issues with your system. > > I can see how our signalling issue would fit into this, but "was run at > the moment the target udt process was freeing shared memory" doesn't > make sense when the process is sitting waiting at a blocking call for > pipes? Is this a different issue or was this all fixed as part of that? > > Regards, > Dan > > _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
