The first Y2038 problem I've personally seen

If you've got sites running AOLserver 3.x running, and you've set the MaxIdle and MaxOpen database timeouts at 1,000,000,000 seconds, then you'll want to go read this thread from the AOLserver developers list.

Almost a week ago (Saturday May 13th at 01:27:28 UTC) the world dipped below the one billion seconds remaining until 32-bit time overflows (in the year 2038) mark.

(For more general information on Y2038, see Wikipedia, Y2038.com, or Google.)

—Michael A. Cleverly
Friday, May 19, 2006 at 16:59

Comment