On Wed, Sep 26, 2012 at 02:53:23PM -0500, DRC wrote: > Isn't that the way it's supposed to behave? > > Still not understanding why you think there's a bug.
Sorry, '1' was too small of a value to be a good example, since it would timeout pretty much immediately. Earlier in the week, we were seeing immediate failures when starting the server with the timeout value set for 3 days in the future. For what ever reason, while troubleshooting it on Monday, the value seemed to be related to a specific value of absolute time, and as wall clock time passed I could reduce the timeout value accordingly to a smaller value (still more than 1 day), and still see the failure. I was able to recreate this on both multiple RHEL 6.2 and OpenSUSE 12.1 systems and multiple users saw the issue. Today, strangely, things are working again. Since it was so repeatable, I assume there was/is an issue with the X server's timeout code and a 2s compliment overflow causing the timeout call back to be called immediately when the idle timeout timer is set. There might be a range of values that triggers the problem. ------------------------------------------------------------------------------ How fast is your code? 3 out of 4 devs don\\\'t know how their code performs in production. Find out how slow your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219672;13503038;z? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ VirtualGL-Users mailing list VirtualGL-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-users
