On Wed, 7 Jul 2010 00:49:57 +0000, Matthew Kitchin (Public) wrote: > I would set the clock to the correct time and disable any and all time > synch mechanisms for your server for now. That is just my opinion. I don't > think any amount of clock drift could be worse than the problems you are > having.
Ok, I'll give that a try. When I tried to get the time back using ntpdate and ntp.org, one interesting thing was that I had to do it at least three times before it finally changed to the right time. [r...@uc new]# ./timeset 6 Jul 20:05:56 ntpdate[5612]: adjust time server 64.251.10.152 offset -0.122409 sec [r...@uc new]# date Tue Jul 6 20:06:00 CDT 2010 [r...@uc new]# ./timeset 6 Jul 20:06:07 ntpdate[5634]: adjust time server 208.94.240.2 offset -0.117984 sec [r...@uc new]# ./timeset 6 Jul 20:06:14 ntpdate[5653]: adjust time server 64.251.10.152 offset -0.108010 sec [r...@uc new]# date Tue Jul 6 20:06:16 CDT 2010 _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
