On 2011-01-17, Miroslav Lichvar <mlich...@redhat.com> 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.
Exactly what resources are you refering to? If you wake it twice a day, it is almost certainly being loaded in from disk, rather than from memory. That is lots of disk reads (libraries, etc) and wear and tear on the disks . If you run it as a daemon, it sits in memory, which may be a concern if you are chronically short of memory. The statement about resource use is so vague as to be useless. And this discussion has already used more resources than ntpd uses in a century (sending out the messages, people reading, and heavens, even replying to the messages, storing them on 10000 computers, etc) . > _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
