Does this mean that WinX machines should ensure that they are rebooted at least every 24 days to avoid overflowing the clock() value until the next version is available?
(Fat chance of going that long between critical security patches!!) ----- Original Message ----- > The problem you were seeing is that clock_t values were overflowing when > setting the timer for server persistence. This caused a race condition > where the server instance would start, discover that it was out of time, > exit, and repeat. This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html
