On 8/24/06 8:53 AM, "Bruce Marshall" <bmarsh@bmarsh.com> wrote:
On Thursday 24 August 2006 02:16, Per Jessen wrote:
Bruce Marshall wrote:
And yes, I used to run ntpd and it worked just fine. Just don't think I need the resource usage required.
Does your NTP really use a lot of resources?? I've never checked, but mine's certainly never caused a problem, not even a lifted eyebrow.
Who knows... ? :-) but it *is* another process, that has to start up at boot, and adds something to the network load, etc etc.... and I think I can do just as well with a couple of ntpdate calls every day.
Not running critical servers here (home) which seems to be the main argument for ntpd.
However, I do have a single server that draws down email to the house and does the firewall stuff. Can that be set up to run ntpd with the other computers on the LAN syncing from that one? I've looked into it but haven't found that it can be done.
Yep. Not too hard at all... Add this to /etc/ntp.conf on the gateway machine: -------- server 0.pool.ntp.org server 1.pool.ntp.org server 2.pool.ntp.org server pool.ntp.org ----------- And then add this to the clients: -------- server <ip of gateway> --------- Do ntpdate on the gateway to get it synced, then start ntp on it. Do ntpdate on the clients to get them synced, then start ntp on them. And you should be good to go. (Things to note: be sure to do `ntpdate <server>` twice, on each server/client, for each server listed; and you may need to adjust firewall rules and/or ntpd settings to get it to listen on an interface other than lo.) The x.pool.ntp.org servers are chosen from the global list, you can get a regional list by drilling down on http://ntp.isc.org/bin/view/Servers/NTPPoolServers