On Mon, 20 May 2002, Jon Travis wrote: > Yeah, it's an interesting one -- apr_time_now() should be GMT though, and > not have anything to do with timezones (not saying they aren't playing a > part in this issue, though). > > This problem manifested itself when a program I was running on Windows > had a hard time communicating with a program under UNIX. Both used > apr_time_now() to determine the current time, and I guess they came up > with different answers.
Didn't someone post a patch for this months ago? I remember it was an extraneous timezone add (or subtract, one of the two), and that it was in the Win32-specific time code. --Cliff -------------------------------------------------------------- Cliff Woolley [EMAIL PROTECTED] Charlottesville, VA
