[ntp:questions] Use ntpd as a daemon so that it continuously disciplines clock, no

Richard B. Gilbert rgilbert88 at comcast.net
Mon Jan 17 14:56:33 UTC 2011


On 1/17/2011 6:20 AM, Miroslav Lichvar wrote:
> On Sat, Jan 15, 2011 at 11:06:43AM -0800, Chris Albertson wrote:
>> As for resources ntpd takes up less then you can measure. After it has
>> been running for a while it takes up almost zero.  Most of the
>> activity is when it first starts up.  So letting it run might use less
>> CPU cycle than starting it serval times per day. Running the crontab
>> scrip involves starting multiple new processes.  this is a very
>> reasource intensive thing to do, much more so then letting ntpd run.
>
> Even when completely idle, ntpd wakes up every second and does quite a
> lot (updating timers, scanning the peer hash table, etc). I'd say that
> starting ntpd two times per day will take much less resources than
> running it continuosly.
>

So running NTPD continuously eats 0.05% of the CPU!  Do you *really* care?




More information about the questions mailing list