Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Time.is

time.is

Post reply on HN
Print view View original

71–80 of 108 posts

Re: Time.is

#71

Post by logic »

dfc wrote: post #42
ComputerGuru wrote: post #41

Earlier quoted context omitted.

I removed the bit about NTP as it was mostly half-baked ramblings. I obviously didn't mean "ping" the tool, rather the process of "pinging" a remote address and gauging the response time, at the most basic. My ntpq -p output: remote refid st t when poll reach delay offset jitter ============================================================================== time.apple.com .INIT. 16 u - 512 0 0.000 0.000 0.000

Your computer has not successfully contacted the time.apple.com server. If it had the refid would not be INIT and your "reach" value would not be 0. what happens if you change your time server to us.pool.ntp.org? (Substitute your country code for "us".) Preferably you should have more than one server. The ntp reference implementation on osx is a little goofy because of the GUI configuration. But I think if you put us…

> But I think if you put us.pool.ntp.org,us.pool.ntp.org,us.pool.ntp.org for the server your computer will try to spin up three ntp connections.

Close, but not quite; ntpd appears to be smart enough to realize you have three identical "server" lines in ntp.conf, and collapses them. Try this instead:

1.us.pool.ntp.org,2.us.pool.ntp.org,3.us.pool.ntp.org

Changing "us" to your country code, of course. Just tested, and it appears to produce the desired behavior.

Re: Time.is

#72

Post by guylhem »

dfc wrote: post #47
guylhem wrote: post #34

I like it a lot. Easy to remember URL. However the services offered are not so good. At least there is no RFC 867 and RFC 868 date on port 37 and port 13. This is deprecated, I know, but rdate is still the easiest way to fix the date on a system which do not require precision. I did run my own minimal daemon on my DSL modem for the various gizmos I have that include busybox (thus rdate) and where recompiling to get a…

rdate is awful that is why NIST killed it. If you want a fire and forget time check: sntp pool.ntp.org

I know rdate is awful but when that's all you have and don't feel like crosscompiling for a device which does not even requires a minute of precision, it does the job.

Technical excellence is not always required, and having more choices usually is a good idea.

Re: Time.is

#73

Post by dfc »

mdda wrote: post #70
dfc wrote: post #44

Earlier quoted context omitted.

ntpdate is dead and is discontinued. Use an actual daemon to govern your time source. I thought redhat installed ntpd or chrony by default. I know chrony is the default for the next fedora release. If you have ntpd/chronyd installed your advice is horrible and not just because you pointed everyone to Virginia Tech's time server.

Thanks : Updated procedure (for Fedora without chronyd/ntpd running already) : # yum install chrony # systemctl enable chronyd.service # systemctl start chronyd.service Sorry if the (working) pointers before were horrible. Hopefully this is more useful - the servers used are {N}.fedora.pool.ntp.org.

chronyd is a lot more mindful of battery/power considerations than ntpd. It is an interesting approach to endpoint time synchronization compared to the ntp reference implementation.

Re: Time.is

#74

Post by dfc »

logic wrote: post #71
dfc wrote: post #42

Earlier quoted context omitted.

Your computer has not successfully contacted the time.apple.com server. If it had the refid would not be INIT and your "reach" value would not be 0. what happens if you change your time server to us.pool.ntp.org? (Substitute your country code for "us".) Preferably you should have more than one server. The ntp reference implementation on osx is a little goofy because of the GUI configuration. But I think if you put us…

> But I think if you put us.pool.ntp.org,us.pool.ntp.org,us.pool.ntp.org for the server your computer will try to spin up three ntp connections. Close, but not quite; ntpd appears to be smart enough to realize you have three identical "server" lines in ntp.conf, and collapses them. Try this instead: 1.us.pool.ntp.org,2.us.pool.ntp.org,3.us.pool.ntp.org Changing "us" to your country code, of course. Just tested, and i…

ntp is not "smart enough to realize you have three identical "server" lines in ntp.conf". Before the addition of the pool directive in 4.2.7 this was the recommended approach (as in recommended by prof. mills, harlan and the rest of the ntp reference implementation team). OSX is trying to be cute and thinks it knows more about ntp than the user.

Try editing /private/etc/ntp.conf and append:

  # use multiple ntp servers
  server us.pool.ntp.org iburst
  server us.pool.ntp.org iburst
  server us.pool.ntp.org iburst
Make sure you have an extra empty line above the comment. There is something goofy about the way osx includes the input from the graphical configuration and what is included in the /private/etc/ntp.conf In order to restart the service you need to disable/re-enable the automatically set time.

Re: Time.is

#75

Post by time_is »

mtr wrote: post #5

Shows incorrect time for Chile. DST isn't until April 28th. http://www.timeanddate.com/news/time/chile-longer-dst-2012.h...

Thanks, we have corrected this now. :)

Re: Time.is

#76

Post by antidaily »

mwexler wrote: post #14

I like Time.gov, personally; it was the first site I ever found around this concept and so it has a soft spot. I keep finding all my physical atomic clock synced clocks (yes, I have more than one, they are cheap these days) disagreeing, sometimes by 2 seconds or more, which makes me laugh (great ideas ruined by poor implementation). I find many of the web sites (listed in comments or the original post) to also differ…

Time.gov is slow and ugly and doesn't work on my phone. Fuck time.gov.

Re: Time.is

#79

Post by lotharbot »

antidaily wrote: post #76
mwexler wrote: post #14

I like Time.gov, personally; it was the first site I ever found around this concept and so it has a soft spot. I keep finding all my physical atomic clock synced clocks (yes, I have more than one, they are cheap these days) disagreeing, sometimes by 2 seconds or more, which makes me laugh (great ideas ruined by poor implementation). I find many of the web sites (listed in comments or the original post) to also differ…

Time.gov is slow and ugly and doesn't work on my phone. Fuck time.gov.

Have you tried the naval observatory master clock at http://tycho.usno.navy.mil/simpletime.html ?

Re: Time.is

#80

Post by samt »

Tell me I'm not the first to see the irony of a page full of comments debating ntp, GPS and atomic clocks, while there are two interesting front page stories about the value of ambitious goals.
Post reply on HN