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