mattKnight
Programmer
The time on our CMS server is drifting (VM hosts are never great at keeping time) and they are not synchronised to any time source.
Avaya's solution is to run the ntpupdate command from a scheduled job within cron. This is not difficult to to carry out, but... Configuring (and starting) ntpd seems a better way - correction of time drift is continious and so any time adjustment is outside the tolerance of CMS and our wfo tools hence I'd not expect any issue with reporting intervals. Obviously, the initial correction of about 5 minutes needs to planned to be mid reporting interval.
So, why do Avaya suggest/recommend/support a solution using cron as opposed to the standard way (ntpd? Is this a hangover form the days of Solaris servers? Are they avoiding vulnerability issues in ntpd? Does any one have an idea why or validate that using ntpd doesn't have negative effects?
Cheers
Take Care
Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
Avaya's solution is to run the ntpupdate command from a scheduled job within cron. This is not difficult to to carry out, but... Configuring (and starting) ntpd seems a better way - correction of time drift is continious and so any time adjustment is outside the tolerance of CMS and our wfo tools hence I'd not expect any issue with reporting intervals. Obviously, the initial correction of about 5 minutes needs to planned to be mid reporting interval.
So, why do Avaya suggest/recommend/support a solution using cron as opposed to the standard way (ntpd? Is this a hangover form the days of Solaris servers? Are they avoiding vulnerability issues in ntpd? Does any one have an idea why or validate that using ntpd doesn't have negative effects?
Cheers
Take Care
Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.