tsmori
6-13-04, 01:05 PM
Here's my problem:
Webserver(mars) time: 2004-06-13 08:59:06
MySQL server(mysql01) time: 2004-06-13 08:57:51
While this may seem somewhat insignificant for probably the vast majority of web-based applications, it's kinda screwing things up for me. In fact, if it was the other way around, i.e. MySQL time in the future, it might be okay, but the database time being over a minute in the past really hoses up my application.
Because this time differential is not always consistant, I can't take account for it programmatically.
If there is any way you all could see using the same time server or somehow synching up the server times, that'd be great. If not, I'll likely have to move my application onto a server that runs both apache and mysql, so the time will always be the same.
Webserver(mars) time: 2004-06-13 08:59:06
MySQL server(mysql01) time: 2004-06-13 08:57:51
While this may seem somewhat insignificant for probably the vast majority of web-based applications, it's kinda screwing things up for me. In fact, if it was the other way around, i.e. MySQL time in the future, it might be okay, but the database time being over a minute in the past really hoses up my application.
Because this time differential is not always consistant, I can't take account for it programmatically.
If there is any way you all could see using the same time server or somehow synching up the server times, that'd be great. If not, I'll likely have to move my application onto a server that runs both apache and mysql, so the time will always be the same.