> Since your clock gets messed up once per hour, and you've previously stated > that you had a cron job that ran every hour that set the time, that cron > job is the most obvious suspect.
I no longer have the additional ntpdate command running, nor anything else doing time controls. Other than sipx functions, there are no others I have installed on the server. I've been checking the time since removing that ntpdate command, both hardware and software times are still dead on since last night. The problem however, persists. > Actually, for debugging purposes right now, it's sufficient to disable > everything that changes the clock and just let the clock free-run. So turn off ntpd then? Are there any other clock related functions going on than ntpd so that I can double check that nothing else is running. Mike
_______________________________________________ sipx-users mailing list [email protected] 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/
