| 1 |
On 26/04/2013 17:54, Nick Khamis wrote: |
| 2 |
> On 4/26/13, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 3 |
>> On 26/04/2013 17:27, Nick Khamis wrote: |
| 4 |
>>> Hello Everyone, |
| 5 |
>>> |
| 6 |
>>> Thank you for the many solutions however, I am totally lost as to which |
| 7 |
>>> would |
| 8 |
>>> be most reliable in a collocation setting vs. office desktop. What we |
| 9 |
>>> would like |
| 10 |
>>> is to set up our own ntp server which other servers and desktops in our |
| 11 |
>>> office |
| 12 |
>>> syncs to. Is this advised? If so, is there a nice tutorial online? |
| 13 |
>> |
| 14 |
>> The subject of time is vastly more complex than anyone ever thinks at |
| 15 |
>> first look. Time servers are tiered and are themselves both clients and |
| 16 |
>> servers... |
| 17 |
>> |
| 18 |
>> So here's what you do: sync everything to your ISP's time servers. |
| 19 |
>> Chances are good they do a better job than you can, just like with DNS |
| 20 |
>> caching. |
| 21 |
>> |
| 22 |
>> When you know more about the subject than you do now, you can venture |
| 23 |
>> into rolling your own. I'm not being rude or funny - time servers are |
| 24 |
>> just one of those things that unless you have special needs and LOTS of |
| 25 |
>> cash, it is so much easier to just let someone else do all the heavy |
| 26 |
>> lifting. |
| 27 |
>> |
| 28 |
>> |
| 29 |
>> -- |
| 30 |
>> Alan McKinnon |
| 31 |
>> alan.mckinnon@×××××.com |
| 32 |
>> |
| 33 |
>> |
| 34 |
>> |
| 35 |
> |
| 36 |
> Hello Alan, |
| 37 |
> |
| 38 |
> Thank you so much for your response, and I totally understand the |
| 39 |
> effort vs. benefit challenge. However, is it really that much |
| 40 |
> trouble/unstable to setup our own ntp |
| 41 |
> server that syncs with our local isp, and have our internal network sync on it? |
| 42 |
|
| 43 |
|
| 44 |
No, it's not THAT much effort. You can get by with installing ntpd on a |
| 45 |
single machine, pointing it at the upstream time server and pointing all |
| 46 |
your clients to it. It's clearly recorded in the config file, you can't |
| 47 |
go wrong. |
| 48 |
|
| 49 |
It's understanding how this weird thing called time works that is the |
| 50 |
issue. Take for example leap seconds..... urggggggggggg... |
| 51 |
|
| 52 |
The basic question I suppose is why do you want to do it this way? What |
| 53 |
do you feel you will gain by doing it yourself? |
| 54 |
|
| 55 |
|
| 56 |
-- |
| 57 |
Alan McKinnon |
| 58 |
alan.mckinnon@×××××.com |
Archives