New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
On one of our servers, looks like ntpd is using about 1.5 megabytes of ram. And over 20 days, the host node's ntpd process has used two minutes of CPU time.
It's extremely easy to set up on Centos:
1. chkconfig ntpd on
2. service ntpd start
3. And then forget about it
Far more effort to run rdate "from time to time manually".
In other words, seems a bit hokey.
See http://disclosed.info/23 for more examples.
Exactly, absolutely correct.
I'd have been extremely surprised if ntpd used anything than a fraction of resources (be it memory, cpu, ....)
But how does one argue with such a response
Quick update, after a brief conversation it was agreed to have ntpd running. But today the time was off again.
Quick back and forth and this response
.... and as far as I can see we are not talking about a 15 year old one-man show here
Pardon my ranting, but such "support" experiences are extremely frustrating
You argue by asking for a refund. No but seriously, unless you are talking PIC micro-controller cloud hosting ntp usage should be negligible.
Why not just put ntpdate pool.ntp.org and hwclock -w into cron?
Not on openvz, and it also wouldnt be really my job to do theirs
That yanks that clock into sync, with time jumps. It's a very coarse way of keeping the clock more-or-less accurate. ntpd makes very gradual adjustments and maintains much better accuracy over the long term.