On 06/28/2014 04:08 PM, Carlos E. R. wrote:

On 2014-06-28 21:41, James Knott wrote:

...

Correction, that should be "National Institute of Science and Technology" (NIST) and not National Bureau of Standards. They had a name change a few years ago. They also run the time web site: http://time.gov/HTML5/ It's exact to the second on my machine, as far I can visually see. If NTP is correctly setup, I would trust it more than a clock displayed in a web page.

That web site says it's adjusted for network delay. Regardless, it agrees with the time signal clock, but my computer clock disagrees with both. I also run "Clocksync" on my Android phone, which also is configured to time.nrc.ca and it agrees with the website and radio clock, but not my computer. So, my computer disagrees with 3 different sources that all agree with each other. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 06/28/2014 04:31 PM, Brandon Vincent wrote:

Try comparing your clocks after running "ntpd -gq". You will probably have to stop the ntpd service first.

I tried that and it's now a full second slow. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 06/28/2014 04:36 PM, Carlos E. R. wrote:

On 2014-06-28 22:33, James Knott wrote:

...

On 06/28/2014 04:31 PM, Brandon Vincent wrote:

...

Try comparing your clocks after running "ntpd -gq". You will probably have to stop the ntpd service first. I tried that and it's now a full second slow. If you run "rcntp ntptimeset" it tells you directly the time difference between your machine clock, and internet, then sets it. Please post the full output of the command.

rcntp ntptimeset 28 Jun 16:43:51 sntp[21152]: Started sntp 2014-06-28 16:43:52.015486 (+0500) +0.000574 +/- 0.005951 secs 2014-06-28 16:43:52.050699 (+0500) +0.000434 +/- 0.007523 secs 2014-06-28 16:43:52.083685 (+0500) -0.000963 +/- 0.010208 secs Time synchronized with time.nrc.ca The computer is still a full second off the other 3. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 06/29/2014 12:32 PM, Andrey Borzenkov wrote:

...

The computer is still a full second off the other 3.

...

May be it is the problem of your clock applet?

That wouldn't surprise me. I'm using the task bar clock in KDE. I fired up my notebook computer, which is also running openSUSE 13.1 and configured for time.nrc.ca. It agrees with my desktop system, but disagrees with the other 3. So, assuming NTP is working properly, then the delay is likely caused by the clock app. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Sun, Jun 29, 2014 at 12:28 PM, Ken Schneider - openSUSE wrote:

I truly do not understand the reason all of the computers need to be set to the "same exact" time. :-)

A time sensitive protocol like Kerberos usually starts to exhibit problems when the time on the KDC and client differs by approximately five minutes. Therefore, I think we could all live with a half second discrepancy. Now to return to the subject, I would like to mention that if your hardware clock has an error of only 0.001% due to temperature or a poorly designed circuit, your clock will be off by a second a day. I'd just check over the motherboard for blown capacitors if you have time, I've seen clocks run oddly when electrolytics fail and increase their ESR. KDE also has a long history of problems with the clock applet. I'd be curious to see a comparsion with a problem like xclock with the -digital or -d flags. Brandon Vincent -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2014-06-29 23:32, James Knott wrote:

On 06/29/2014 04:01 PM, Brandon Vincent wrote:

Xclock in digital mode shows only the time when it was started. It does not advance, so you have no idea how accurate it is. There used to be kclock, but that's long gone. I was looking in software management for a suitable clock, but none were listed.

Suggestions?

gkrellm? -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

On 2014-06-29 21:28, Ken Schneider - openSUSE wrote:

I truly do not understand the reason all of the computers need to be set to the "same exact" time. :-)

For instance... It allows comparing logs between machines. If you have to sync files between computers, their correct timestamps are important, or you have to compare file contents to make sure. By the way, your machine IS (apparently) synced up to a second accuracy, I can tell that from here :-) (your email took took 14 seconds to reach my machine) -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

On 2014-06-30 00:31, Ken Schneider - openSUSE wrote:

On 06/29/2014 04:58 PM, Carlos E. R. pecked at the keyboard and wrote:

I get all that Carlos, but we are talking about a difference of /one/ second here.

Ok, but if there is one second difference, it means that ntp is not working, so the clock can start drift way more since that moment.

The speed at which an email reaches my "machine" is irrelevant, it is the time it takes to reach my inbox at the ISP server that matters. Besides I only poll my ISP server every 10 seconds. :-)

No, it is not that what I meant, but that I was able to find that out because you are, apparently, synced properly to internet time. If you were not synced, or the intermediate steps weren't, I couldn’t track if one of those steps delays email. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

On 06/29/2014 05:29 PM, James Knott pecked at the keyboard and wrote:

On 06/29/2014 03:28 PM, Ken Schneider - openSUSE wrote:

...

I truly do not understand the reason all of the computers need to be set to the "same exact" time. :-)

How else will you know when it's time to go watch the game shows on TV? ;-)

Not the game shows but the American football games. :-) -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Ken Schneider - openSUSE wrote:

I truly do not understand the reason all of the computers need to be set to the "same exact" time. :-) If you share files between them and use them for make or if you sync them with 'rsync', then not having them accurate to the second will create problems.

rsync even has a special option to allow for being off by 1 second or more. FAT32 based file systems used to only keep time to the nearest 2 seconds. That caused problems when you rsync'ed files back and forth - like rsyncing once, followed by a 2nd, and noting that some number of files need transferring again (even though they were just transfered). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2014-06-28 22:08, Carlos E. R. wrote:

On 2014-06-28 21:41, James Knott wrote:

It's exact to the second on my machine, as far I can visually see. If NTP is correctly setup, I would trust it more than a clock displayed in a web page.

A rough time check can be done on this email headers: At my machine: Received: from localhost (localhost [127.0.0.1]) by Telcontar.valinor (Postfix) for ; Sat, 28 Jun 2014 22:08:15 +0200 (CEST) at my ISP: Received: from Telcontar.valinor (79.150.228.90) by smtp.movistar.es Sat, 28 Jun 2014 20:08:16 +0000 at openSUSE: Received: from smtp.movistar.es by mx2.suse.de (Postfix) Sat, 28 Jun 2014 20:08:17 +0000 (UTC) Ok, a second difference on each, but that cab be processing delays. However, polling Novell nttp server, I see in the logs: <7.7> 2014-06-28 22:13:15 Telcontar fetchnews 6367 - - <200 Welcome to forums.novell.com! (Typhoon v2.1.2.394) <7.6> 2014-06-28 22:13:15 Telcontar fetchnews 6367 - - nntp.novell.com: connected to 130.57.2.15:119, reply: 200 <7.7> 2014-06-28 22:13:15 Telcontar fetchnews 6367 - - >MODE READER <7.7> 2014-06-28 22:13:15 Telcontar fetchnews 6367 - - <200 Welcome to forums.novell.com! (Typhoon v2.1.2.394) <7.6> 2014-06-28 22:13:15 Telcontar fetchnews 6367 - - nntp.novell.com: 0 articles posted. <7.7> 2014-06-28 22:13:15 Telcontar fetchnews 6367 - - >DATE <7.7> 2014-06-28 22:13:15 Telcontar fetchnews 6367 - - <111 20140628201314 <7.7> 2014-06-28 22:13:15 Telcontar fetchnews 6367 - - check_date: nntp.novell.com: server time 1403986394, our time 1403986395 See? The last line is a time check. Of course, I'm assuming that nntp.novell.com keeps the correct time, and if it is, we are at most at one second difference. I suppose, the more precise data would be this: Telcontar:~ # ntptime ntp_gettime() returns code 0 (OK) time d759a252.9f4080c0 Sat, Jun 28 2014 22:21:38.622, (.622078977), maximum error 282753 us, estimated error 1316 us, TAI offset 0 ntp_adjtime() returns code 0 (OK) modes 0x0 (), offset 1637.901 us, frequency -40.757 ppm, interval 1 s, maximum error 282753 us, estimated error 1316 us, status 0x6001 (PLL,NANO,MODE), time constant 10, precision 0.001 us, tolerance 500 ppm, Telcontar:~ # Or rather this: Telcontar:~ # rcntp ntptimeset 28 Jun 22:30:26 sntp[7182]: Started sntp 2014-06-28 22:30:26.105689 (-0100) -0.001008 +/- 0.109039 secs Time synchronized with AmonLanc.valinor Telcontar:~ # -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2014-07-03 at 11:35 +0200, Ruediger Meier wrote:

You can check the diff to ntpserver like this

$ sntp time.nrc.ca 3 Jul 11:26:13 sntp[7989]: Started sntp 2014-07-03 11:26:13.539189 (-0100) -0.008495 +/- 0.005508 secs 2014-07-03 11:26:13.670113 (-0100) -0.008351 +/- 0.006958 secs 2014-07-03 11:26:13.801026 (-0100) -0.008343 +/- 0.009430 secs

So in this example my local clock is about 8 ms ahead of ntp server (+/- correctness).

Note there are 3 lines output! One for each machine where time.nrc.ca resoves to.

cer@Telcontar:~> sntp time.nrc.ca 3 Jul 11:57:26 sntp[26307]: Started sntp 2014-07-03 11:57:27.147191 (-0100) +0.427058 +/- 0.005676 secs 2014-07-03 11:57:27.323066 (-0100) +0.295449 +/- 0.007294 secs 2014-07-03 11:57:27.498973 (-0100) +0.295515 +/- 0.007553 secs 3 Jul 11:57:27 sntp[26307]: Can't open KOD db file /var/db/ntp-kod for writing! cer@Telcontar:~> Well, they do not agree with one another, here... about 0.13 second difference from the first one to the second one. Also, I can see that ntp doesn't handle hibernation properly, looking at the log: 2 Jul 11:27:45 ntpd[8726]: 0.0.0.0 c618 08 no_sys_peer 3 Jul 00:36:56 ntpd[8726]: 0.0.0.0 0613 03 spike_detect +0.609002 s 3 Jul 00:42:37 ntpd[8726]: 0.0.0.0 061c 0c clock_step +0.604500 s 3 Jul 00:42:37 ntpd[8726]: 0.0.0.0 0615 05 clock_sync 3 Jul 00:42:38 ntpd[8726]: 0.0.0.0 c618 08 no_sys_peer 3 Jul 11:59:53 ntpd[8726]: 0.0.0.0 0613 03 spike_detect +0.301752 s I have awakened the machine at 11:29. Telcontar:~ # rcntp ntptimeset 3 Jul 12:02:31 sntp[26619]: Started sntp 2014-07-03 12:02:31.718722 (-0100) +0.297341 +/- 0.131897 secs Time synchronized with AmonLanc.valinor Telcontar:~ # Now: cer@Telcontar:~> sntp time.nrc.ca 3 Jul 12:02:56 sntp[26653]: Started sntp 2014-07-03 12:02:56.744866 (-0100) +0.001358 +/- 0.008820 secs 2014-07-03 12:02:56.992912 (-0100) -0.036150 +/- 0.005997 secs 2014-07-03 12:02:57.165804 (-0100) +0.001231 +/- 0.007751 secs 3 Jul 12:02:57 sntp[26653]: Can't open KOD db file /var/db/ntp-kod for writing! cer@Telcontar:~> And those 3 time servers agree - this can not be. Even if my clock was off by .3 seconds, the difference to any good ntp server should be about the same, and can not change that lot with a measurement taken just five minutes later (I mean the difference between line and two, which is now 0.037S). - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlO1LG4ACgkQtTMYHG2NR9Vq6ACfQGPdrHjqE2+u81f+hdqGMcnh hNoAniy8Zm4jrytlQmnSiPcf0u5lOHWG =hybZ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2014-07-03 at 12:32 +0200, Ruediger Meier wrote:

BTW you can also query your local ntp daemon for all used ntp servers.

$ ntpq -p localhost remote refid st t when poll reach delay offset jitter ============================================================================== +homer.ga.local 130.149.17.21 2 u 286 1024 377 0.744 -2.952 0.299 *glaukos.ga.loca 130.149.17.21 2 u 294 1024 377 0.098 3.060 0.174

These offsets (in ms) may be more correct than sntp's because your ntpd is watching the servers for a long time and probably includes some statistics about correctness etc. Also you see that your ntpd is setting the time to some kind of average of all used ntp servers.

It says the same as "--peers". Telcontar:~ # ntpq --peers remote refid st t when poll reach delay offset jitter ============================================================================== LOCAL(0) .LOCL. 10 l 12h 64 0 0.000 0.000 0.000 +AmonLanc.valino 37.187.7.160 3 u 625 1024 377 0.301 0.002 159.044 +numeros.vectric 130.206.3.166 2 u 942 1024 377 60.068 -0.237 164.389 - -din-190-249-227 150.214.94.5 2 u 620 1024 377 110.784 17.104 158.689 - -81.184.154.182. 88.198.230.201 3 u 531 1024 127 115.782 18.547 133.764 +PTV.EXA-PTG.ES 150.214.94.5 2 u 502 1024 127 69.733 3.028 17.855 #ntppublic.uzh.c 130.60.159.8 4 u 990 1024 377 106.483 304.418 300.306 #z.bsod.fr 138.195.130.62 3 u 1026 1024 377 84.755 298.845 284.814 - -www.bhay.org 212.82.32.15 2 u 484 1024 377 82.921 -0.234 164.306 *guti.uc3m.es 130.206.3.166 2 u 608 1024 127 67.194 -0.455 3.012 - -time2.ethz.ch .PPS. 1 u 1008 1024 377 105.898 305.147 269.285 +dalek.roflcopte 195.83.222.27 2 u 34 1024 377 74.532 1.977 119.042 +dnscache-london 140.203.204.77 2 u 453 1024 127 89.214 -4.351 154.875 #time.nrc.ca 132.246.11.231 2 u 431 1024 377 177.779 -1.883 159.993 Telcontar:~ # ntpq -p localhost remote refid st t when poll reach delay offset jitter ============================================================================== LOCAL(0) .LOCL. 10 l 12h 64 0 0.000 0.000 0.000 +AmonLanc.valino 37.187.7.160 3 u 641 1024 377 0.301 0.002 159.044 +numeros.vectric 130.206.3.166 2 u 958 1024 377 60.068 -0.237 164.389 - -din-190-249-227 150.214.94.5 2 u 636 1024 377 110.784 17.104 158.689 - -81.184.154.182. 88.198.230.201 3 u 547 1024 127 115.782 18.547 133.764 +PTV.EXA-PTG.ES 150.214.94.5 2 u 518 1024 127 69.733 3.028 17.855 #ntppublic.uzh.c 130.60.159.8 4 u 1006 1024 377 106.483 304.418 300.306 #z.bsod.fr 138.195.130.62 3 u 1042 1024 377 84.755 298.845 284.814 - -www.bhay.org 212.82.32.15 2 u 500 1024 377 82.921 -0.234 164.306 *guti.uc3m.es 130.206.3.166 2 u 624 1024 127 67.194 -0.455 3.012 - -time2.ethz.ch .PPS. 1 u 1024 1024 377 105.898 305.147 269.285 +dalek.roflcopte 195.83.222.27 2 u 50 1024 377 74.532 1.977 119.042 +dnscache-london 140.203.204.77 2 u 469 1024 127 89.214 -4.351 154.875 #time.nrc.ca 132.246.11.231 2 u 447 1024 377 177.779 -1.883 159.993 Telcontar:~ - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlO1NFMACgkQtTMYHG2NR9WVzgCfS4hTSaH6YmVXmx3e75z9T2gl lIMAnAuUsQGYtsV8YRnz7Ed/E2jzdAQk =gW2J -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2014-06-28 22:42, James Knott wrote:

I saw that notice years ago. It says they switched from the old "time" protocol to NTP, which is what I'm using. Also, given it's a primary time source, equivalent to the NIST in the U.S., it should be fully accurate. As for pool servers, they can be slightly less accurate, IIRC. The University of Toronto has two servers, "tick" and "tock" ;-).

You should not set up a single server to query, but several. Like 8. Include those you like, but add a few from the pool. Don't worry, ntp knows how to weed out the bad ones.

Of course, this doesn't change the fact that an Android phone, also configured to time.nrc.ca, agrees with the 2 NIST sources. The only variable here that could be causing the difference is openSUSE. My phone is connected, via WiFi, to the same network as my computer.

My Android phone automatically syncs to my mobile telephone provider, as far as I know. I did not set it up myself, there is no config (only "automatic" or "manual", which means entering a time. I don't know of a way to display seconds in my phone. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

On 2014-06-28 22:32, John Andersen wrote:

You don't need a Canadian one, even the North American pool NTP sources work fine you set your timezone. (And its generally frowned upon to point all your machines at the either Research Canada or NIST, because of server load. That is what pool NTP servers are for, and also most universities have NTP servers synced to the national servers.

True. I have it like this: server 0.pool.ntp.org server 1.pool.ntp.org server 2.pool.ntp.org server 3.pool.ntp.org which works fine. Or, you can use: server 0.ca.pool.ntp.org server 1.ca.pool.ntp.org server 2.ca.pool.ntp.org server 3.ca.pool.ntp.org which gives you Canadian servers. Or, you use a combination, like 4 Canadian servers, and 4 international servers. Don't worry, the ntp daemon is clever enough to find out on the list which are the best ones, and which to discard. In my case, the command: Telcontar:~ # rcntp ntptimeset 28 Jun 22:43:41 sntp[7729]: Started sntp 2014-06-28 22:43:41.419620 (-0100) -0.000659 +/- 0.120956 secs Time synchronized with AmonLanc.valinor Telcontar:~ # says that the best current one now is a local network machine, that runs 24*7. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

On 06/28/2014 04:47 PM, Carlos E. R. wrote:

On 2014-06-28 22:32, John Andersen wrote:

...

You don't need a Canadian one, even the North American pool NTP sources work fine you set your timezone. (And its generally frowned upon to point all your machines at the either Research Canada or NIST, because of server load. That is what pool NTP servers are for, and also most universities have NTP servers synced to the national servers. True. I have it like this:

server 0.pool.ntp.org server 1.pool.ntp.org server 2.pool.ntp.org server 3.pool.ntp.org

which works fine. Or, you can use:

server 0.ca.pool.ntp.org server 1.ca.pool.ntp.org server 2.ca.pool.ntp.org server 3.ca.pool.ntp.org

which gives you Canadian servers. Or, you use a combination, like 4 Canadian servers, and 4 international servers. Don't worry, the ntp daemon is clever enough to find out on the list which are the best ones, and which to discard.

In my case, the command:

Telcontar:~ # rcntp ntptimeset 28 Jun 22:43:41 sntp[7729]: Started sntp 2014-06-28 22:43:41.419620 (-0100) -0.000659 +/- 0.120956 secs Time synchronized with AmonLanc.valinor Telcontar:~ #

says that the best current one now is a local network machine, that runs 24*7.

Well, I added all 8 of those servers and ran that command. It says time.nrc.ca is the best. I'm still about a second off. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 6/28/2014 4:10 PM, Carlos E. R. wrote:

On 2014-06-29 00:08, James Knott wrote:

...

Well, I added all 8 of those servers and ran that command. It says time.nrc.ca is the best. I'm still about a second off.

You should stop the service, run "rcntp ntptimeset", then "rcntp start".

And take that opportunity to delete time.nrc.ca from the list. Note that ntp has a built in preference for lower tier numbered servers. time.nrc.ca may be winning just because it is the lowest tier (1), not because it is more accurate. Its unusual for the odd-man-out to win this type of selection. - -- _____________________________________ - ---This space for rent--- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) iEYEARECAAYFAlOvU88ACgkQv7M3G5+2DLLxRgCfX7Uxnt7d2FhqaMgsk7r6qWz5 sFoAoI9M4qHhGfyRlFYNq5/W/tVATtgB =HMBr -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Sun 29 Jun 2014 02:09:31 AM CDT, Carlos E. R. wrote:

On 2014-06-29 01:46, John Andersen wrote:

...

On 6/28/2014 4:10 PM, Carlos E. R. wrote:

...

And take that opportunity to delete time.nrc.ca from the list.

Note that ntp has a built in preference for lower tier numbered servers. time.nrc.ca may be winning just because it is the lowest tier (1), not because it is more accurate. Its unusual for the odd-man-out to win this type of selection.

I have added "time.nrc.ca" to my list, and restarted the daemon, to see what happens.

However, despite the daemon being running, I can not query its status:

Telcontar:~ # rcntp status localhost: timed out, nothing received ***Request timed out

Checking for network time protocol daemon (NTPD):

running ntp.service - LSB: Network time protocol daemon (ntpd) Loaded: loaded (/etc/init.d/ntp) Drop-In: /run/systemd/generator/ntp.service.d └─50-insserv.conf-$time.conf Active: active (running) since Sun 2014-06-29 01:55:58 CEST; 19s ago

ntpq --peers also times out. :-?

Telcontar:~ # ntpq -d -d -d --peers Opening host localhost Sending 12 octets Sending 12 octets localhost: timed out, nothing received ***Request timed out Telcontar:~ #

So I can not find out what it may say about time.nrc.ca

Hi Probably good it does.... I'm guessing you have added the restrict? #With respect to CVE-2013-5211 and #http://lists.opensuse.org/opensuse-security-announce/2014-01/msg00005.html restrict default noquery -- Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890) openSUSE 13.1 (Bottle) (x86_64) 3.10.1 Kernel 3.11.10-17-desktop up 7:55, 3 users, load average: 0.40, 0.55, 0.53 CPU Intel® B840@1.9GHz | GPU Intel® Sandybridge Mobile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 6/28/2014 5:35 PM, Carlos E. R. wrote:

On 2014-06-29 02:17, Malcolm wrote:

...

On Sun 29 Jun 2014 02:09:31 AM CDT, Carlos E. R. wrote:

...

...

So I can not find out what it may say about time.nrc.ca

Hi Probably good it does.... I'm guessing you have added the restrict?

#With respect to CVE-2013-5211 and #http://lists.opensuse.org/opensuse-security-announce/2014-01/msg00005.html restrict default noquery

Oh, right! I had forgotten.

Anyway, I guess I can disable it temporarily, it is no accessible from outside.

Telcontar:~ # ntpq --peers remote refid st t when poll reach delay offset jitter ============================================================================== *LOCAL(0) .LOCL. 10 l 30 64 1 0.000 0.000 0.000 din-190-249-227 150.214.94.5 2 u 29 64 1 105.051 36.855 0.000 84.88.69.32 193.67.79.202 2 u 28 64 1 91.214 -8.605 0.000 81.184.154.182. .INIT. 16 u - 64 0 0.000 0.000 0.000 masip.celingest 158.227.98.15 2 u 26 64 1 74.805 0.445 0.000 91.235.212.22 .INIT. 16 u - 64 0 0.000 0.000 0.000 de-ntp01.swiss- 108.94.7.96 3 u 24 64 1 86.666 -2.623 0.000 merzhin.deuza.n 195.83.222.27 2 u 23 64 1 76.640 0.355 0.000 rs2.connect.cus .INIT. 16 u - 64 0 0.000 0.000 0.000 vps01.roethof.n .INIT. 16 u - 64 0 0.000 0.000 0.000 Telcontar:~ #

It does not appear that "time.nrc.ca" is in there :-?

NONE of those are being used. Your local clock is all that is being used right now. How long has it been since you restarted? You have too give it some time. It could take 15 minutes to half an hour. - -- _____________________________________ - ---This space for rent--- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) iEYEARECAAYFAlOvbP0ACgkQv7M3G5+2DLJvAgCeJDNWS+uwZuA3vCEE9oz/Mkwb O7QAoIIU33FB3AoLVsm+aALYUgxF+O1J =b8E2 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 06/28/2014 07:46 PM, John Andersen wrote:

not because it is more accurate

Ummm... As I mentioned earlier, that's from the National Research Council, which provides Canada's primary time standard. If they're wrong then they've got a serious problem. Also, as I mentioned, my Android phone, running clocksync from that same server, agreed with the 2 NIST sources. So, if 3 agree and one doesn't, where do you think the problem is? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

El 29/06/14 08:15, James Knott escribió:

On 06/29/2014 12:43 AM, Cristian Rodríguez wrote:

...

Websites are not a good indicator.. there are a number of ways it could be delayed.. just use..

That NIST web page says it compensates for network delay, just as NTP does. Regardless, of the four devices, only my computer disagrees. My cell phone, using the same NTP site as my computer, agrees with the web site and my radio clock. Why the difference, when 2 devices are using the same NTP server?

The difference may be because of a number of factors but most likely a) the NTP client has not settled yet, it may take hours in the worst case scenario. b) you computer's clock is unstable..does the kernel log says something about it ? -- Cristian "I don't know the key to success, but the key to failure is trying to please everybody." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2014-06-29 14:20, James Knott wrote:

I did that last night and it's still about a second off.

Add more servers, run "rcntp status" now and then to find out how it goes. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2014-06-29 at 13:17 -0400, James Knott wrote:

I as of last night, I have 10 servers listed. Is that enough?

Don't worry about setting "too many". ntpd does a selection, weeds the bad ones, and if still too many, discards a few.

rcntp status remote refid st t when poll reach delay offset jitter ============================================================================== -time.nrc.ca 132.246.11.233 2 u 606 1024 377 32.433 9.859 1.569 -zero.gotroot.ca 226.54.28.63 2 u 178 1024 377 71.056 4.566 1.640 -mongrel.ahem.ca 164.244.221.197 2 u 124 1024 377 36.192 3.825 1.691 *2620:10a:800f:: .PPS. 1 u 149 1024 377 53.368 2.071 1.164 +vela.z0p.org 206.108.0.131 2 u 126 1024 377 17.076 2.597 6.189 +napa.ruselabs.c 216.218.254.202 2 u 45m 1024 374 76.059 0.476 1.610 -falcon.ca.us.sl 199.102.46.73 2 u 526 1024 375 83.738 8.285 2.139 +ntp-stm32.glads .GPS. 1 u 744 1024 377 64.199 0.047 2.568 -framboise.hoopy 128.4.1.1 2 u 557 1024 377 29.139 3.306 1.687 -time1.chu.nrc.c 209.87.233.50 2 u 426 1024 377 25.409 4.108 2.246 localhost .INIT. 16 l - 1024 0 0.000 0.000 0.000

Well, your own daemon is in "init" status. In http://rimuhosting.com/howto/ntp.jsp there is an explanation of that, although not related to "localhost" (incomplete connection?). This may be because you are listing "localhost" as a server in ntp.conf. However, you have one remote server, via IPv6 marked with *, and it is stratum 1. See that "time.nrc.ca" is rejected. Code Message T Description 0 sel_reject discarded as not valid (TEST10-TEST13) 1 sel_falsetick x discarded by intersection algorithm 2 sel_excess . discarded by table overflow (not used) 3 sel_outlyer - discarded by the cluster algorithm 4 sel_candidate + included by the combine algorithm 5 sel_backup # backup (more than tos maxclock sources) 6 sel_sys.peer * system peer 7 sel_pps.peer o PPS peer (when the prefer peer is valid) - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlOwfwQACgkQtTMYHG2NR9WHnwCfT4wxp1xh5SpjvpR3JzJH+jpA miYAnRhFuyD/KZBreBooduadpwnQyvm+ =E8U/ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 06/29/2014 05:03 PM, Carlos E. R. wrote:

However, you have one remote server, via IPv6 marked with *, and it is stratum 1. See that "time.nrc.ca" is rejected.

I have no idea what server that is. It's certainly not on my IPv6 subnet. Where does it say time.nrc.ca is rejected? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2014-06-29 06:43, Cristian Rodríguez wrote:

Websites are not a good indicator.. there are a number of ways it could be delayed.. just use..

# by default act only as a basic NTP client restrict -4 default nomodify nopeer noquery notrap restrict -6 default nomodify nopeer noquery notrap # allow NTP messages from the loopback address, useful for debugging restrict 127.0.0.1 restrict ::1

(if you do not use those lines, you will become a ntp amplification for a D.D.O.S that is beign exploited in the wild)

Question: as my router supposedly blocks ntp, could I just use instead: restrict default noquery restrict 127.0.0.1 restrict ::1 So that local machines have more complete access? -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

James Knott wrote:

On 06/29/2014 12:43 AM, Cristian Rodríguez wrote:

...

# by default act only as a basic NTP client restrict -4 default nomodify nopeer noquery notrap restrict -6 default nomodify nopeer noquery notrap # allow NTP messages from the loopback address, useful for debugging restrict 127.0.0.1 restrict ::1

Is that necessary for a system that's behind a firewall?

Provided port 123 is blocked, not really, but it doesn't hurt.

Will it affect the computer operating as a server?

Probably not, but your provider will be in touch quite quickly. -- Per Jessen, Zürich (18.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

James Knott wrote:

On 07/02/2014 03:35 PM, Per Jessen wrote:

...

...

...

Will it affect the computer operating as a server? Probably not, but your provider will be in touch quite quickly.

I was referring to a server on my local network only. The only servers I have facing the Internet are IMAPS and SSH, though I have had a VPN in the past.

If your server was being abused, you probably wouldn't notice and it's functionality wouldn't suffer either. We had the issue a couple of months ago. -- Per Jessen, Zürich (18.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 29/06/14 16:47, Basil Chupin wrote:

On 29/06/14 05:37, James Knott wrote:

...

I run NTP to set my computer clock and the time is displayed on the task bar. I can also check the time on a U.S. government web site and on a clock that's synced to WWVB, the U.S. National Bureau of Standards time signal. My computer clock tends to be about a half second behind the other two. I though NTP was supposed to be able to do better than that. I connect to the time.nrc.ca NTP server, which is run by the National Research Council in Ottawa, which is the primary time standard for Canada.

Mein Gott! A full, but about, 1/2 second behind!

Stick with the computer clock, James - you've gained a 1/2 second in life-time before you go to be with the angels :-) .

BC

Forgot to mention that your problem has added 30 (now 32) posts on the subject. I guess that it is raining outside or something and people don't have much of anything else to do. I know I don't as it is damn cold outside! :-) BC -- Using openSUSE 13.1, KDE 4.13.2 & kernel 3.15.1-2 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R. wrote:

On 2014-06-29 08:49, Basil Chupin wrote:

...

Forgot to mention that your problem has added 30 (now 32) posts on the subject.

Well, it is curious that with ntpd running the clock is not correct to 0.01 seconds.

...

I guess that it is raining outside or something and people don't have much of anything else to do. I know I don't as it is damn cold outside! :-)

Please ship some of that cold to me. It is 30ºC here, inside - outside maybe 34.

Well, since water freezes at 32F, switch part of the room to Fahrenheit. :-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org