On 26/04/2013 17:54, Nick Khamis wrote: > On 4/26/13, Alan McKinnon <alan.mckin...@gmail.com> wrote: >> On 26/04/2013 17:27, Nick Khamis wrote: >>> Hello Everyone, >>> >>> Thank you for the many solutions however, I am totally lost as to which >>> would >>> be most reliable in a collocation setting vs. office desktop. What we >>> would like >>> is to set up our own ntp server which other servers and desktops in our >>> office >>> syncs to. Is this advised? If so, is there a nice tutorial online? >> >> The subject of time is vastly more complex than anyone ever thinks at >> first look. Time servers are tiered and are themselves both clients and >> servers... >> >> So here's what you do: sync everything to your ISP's time servers. >> Chances are good they do a better job than you can, just like with DNS >> caching. >> >> When you know more about the subject than you do now, you can venture >> into rolling your own. I'm not being rude or funny - time servers are >> just one of those things that unless you have special needs and LOTS of >> cash, it is so much easier to just let someone else do all the heavy >> lifting. >> >> >> -- >> Alan McKinnon >> alan.mckin...@gmail.com >> >> >> > > Hello Alan, > > Thank you so much for your response, and I totally understand the > effort vs. benefit challenge. However, is it really that much > trouble/unstable to setup our own ntp > server that syncs with our local isp, and have our internal network sync on > it?
No, it's not THAT much effort. You can get by with installing ntpd on a single machine, pointing it at the upstream time server and pointing all your clients to it. It's clearly recorded in the config file, you can't go wrong. It's understanding how this weird thing called time works that is the issue. Take for example leap seconds..... urggggggggggg... The basic question I suppose is why do you want to do it this way? What do you feel you will gain by doing it yourself? -- Alan McKinnon alan.mckin...@gmail.com
