Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #198485 > unrolled thread
| Started by | Fred <fred@blakemfg.com> |
|---|---|
| First post | 2018-08-09 16:40 +0200 |
| Last post | 2018-08-09 16:50 +0200 |
| Articles | 4 on this page of 44 — 16 participants |
Back to article view | Back to linux.debian.user
What time is it, really? Fred <fred@blakemfg.com> - 2018-08-09 16:40 +0200
Re: What time is it, really? Martin <keine-eile@online.de> - 2018-08-09 16:40 +0200
Re: What time is it, really? Greg Wooledge <wooledg@eeg.ccf.org> - 2018-08-09 16:40 +0200
Re: What time is it, really? Jim Popovitch <jim@k4vqc.com> - 2018-08-09 17:00 +0200
Re: What time is it, really? Greg Wooledge <wooledg@eeg.ccf.org> - 2018-08-09 17:10 +0200
Re: What time is it, really? Jim Popovitch <jim@k4vqc.com> - 2018-08-09 17:10 +0200
Re: What time is it, really? john doe <johndoe65534@mail.com> - 2018-08-09 20:40 +0200
Re: What time is it, really? Brian <ad44@cityscape.co.uk> - 2018-08-09 21:50 +0200
Re: What time is it, really? Fred <fred@blakemfg.com> - 2018-08-09 23:40 +0200
Re: What time is it, really? Shea Alterio <krusete@gmail.com> - 2018-08-10 00:00 +0200
Re: What time is it, really? David Wright <deblis@lionunicorn.co.uk> - 2018-08-10 17:20 +0200
Re: What time is it, really? Michael Stone <mstone@debian.org> - 2018-08-10 17:40 +0200
Re: What time is it, really? David Wright <deblis@lionunicorn.co.uk> - 2018-08-10 21:50 +0200
Re: What time is it, really? Fred <fred@blakemfg.com> - 2018-08-10 18:40 +0200
Re: What time is it, really? Brian <ad44@cityscape.co.uk> - 2018-08-10 19:50 +0200
Re: What time is it, really? Fekete Tamás <fektom@gmail.com> - 2018-08-10 19:50 +0200
Re: What time is it, really? Greg Wooledge <wooledg@eeg.ccf.org> - 2018-08-10 20:10 +0200
Re: What time is it, really? Gene Heskett <gheskett@shentel.net> - 2018-08-10 20:20 +0200
Re: What time is it, really? Michael Stone <mstone@debian.org> - 2018-08-10 23:00 +0200
Re: What time is it, really? Fekete Tamás <fektom@gmail.com> - 2018-08-11 11:10 +0200
Re: What time is it, really? David Wright <deblis@lionunicorn.co.uk> - 2018-08-10 22:40 +0200
Re: What time is it, really? Gene Heskett <gheskett@shentel.net> - 2018-08-09 17:10 +0200
Re: What time is it, really? Darac Marjal <mailinglist@darac.org.uk> - 2018-08-09 17:20 +0200
Re: What time is it, really? Greg Wooledge <wooledg@eeg.ccf.org> - 2018-08-09 18:00 +0200
Re: What time is it, really? Andre Majorel <aym-naibed@teaser.fr> - 2018-08-09 19:10 +0200
Re: What time is it, really? Nicolas George <george@nsup.org> - 2018-08-09 19:20 +0200
Re: What time is it, really? Michael Stone <mstone@debian.org> - 2018-08-09 20:00 +0200
Re: What time is it, really? deloptes <deloptes@gmail.com> - 2018-08-10 01:30 +0200
Re: What time is it, really? Nicolas George <george@nsup.org> - 2018-08-09 16:50 +0200
OT: What time is it, really? Martin <keine-eile@online.de> - 2018-08-09 17:10 +0200
Re: OT: What time is it, really? Martin <keine-eile@online.de> - 2018-08-09 17:20 +0200
Re: OT: What time is it, really? Nicolas George <george@nsup.org> - 2018-08-09 17:50 +0200
Re: OT: What time is it, really? Martin <keine-eile@online.de> - 2018-08-09 18:10 +0200
Re: OT: What time is it, really? Gene Heskett <gheskett@shentel.net> - 2018-08-09 18:20 +0200
Re: OT: What time is it, really? Martin <keine-eile@online.de> - 2018-08-09 18:30 +0200
Re: OT: What time is it, really? Gene Heskett <gheskett@shentel.net> - 2018-08-09 19:40 +0200
Re: OT: What time is it, really? Anders Andersson <pipatron@gmail.com> - 2018-08-10 12:00 +0200
Re: OT: What time is it, really? Gene Heskett <gheskett@shentel.net> - 2018-08-10 13:50 +0200
Re: OT: What time is it, really? Nicolas George <george@nsup.org> - 2018-08-09 17:20 +0200
Re: What time is it, really? Fred <fred@blakemfg.com> - 2018-08-09 18:50 +0200
Re: What time is it, really? Nicolas George <george@nsup.org> - 2018-08-09 19:00 +0200
Re: What time is it, really? Greg Wooledge <wooledg@eeg.ccf.org> - 2018-08-09 19:00 +0200
Re: What time is it, really? Michael Stone <mstone@debian.org> - 2018-08-09 20:00 +0200
Re: What time is it, really? Gene Heskett <gheskett@shentel.net> - 2018-08-09 16:50 +0200
Page 3 of 3 — ← Prev page 1 2 [3]
| From | Nicolas George <george@nsup.org> |
|---|---|
| Date | 2018-08-09 19:00 +0200 |
| Message-ID | <wkWs2-5Un-7@gated-at.bofh.it> |
| In reply to | #198504 |
[Multipart message — attachments visible in raw view] — view raw
Fred (2018-08-09): > I think you may be right. It seems a stupid response from ntpdate since I > asked the time from the server. It gave you the information. > So, ntpdate maybe isn't what I should be > using. That is what many people have just told you. > There was a discussion about time services on this list some time ago and at > that time I decided chrony should be used so I will try it next. I don't > want a service that keeps banging on the server. Since you do not have the skill yourself, trust the default configuration. Regards, -- Nicolas George
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2018-08-09 19:00 +0200 |
| Message-ID | <wkWs2-5Un-9@gated-at.bofh.it> |
| In reply to | #198504 |
On Thu, Aug 09, 2018 at 09:36:33AM -0700, Fred wrote: > I don't > want a service that keeps banging on the server. Once a day seems > reasonable to me. It's not.
[toc] | [prev] | [next] | [standalone]
| From | Michael Stone <mstone@debian.org> |
|---|---|
| Date | 2018-08-09 20:00 +0200 |
| Message-ID | <wkXo5-6uK-3@gated-at.bofh.it> |
| In reply to | #198504 |
On Thu, Aug 09, 2018 at 09:36:33AM -0700, Fred wrote: >I think you may be right. It seems a stupid response from ntpdate >since I asked the time from the server. So, ntpdate maybe isn't what >I should be using. ntpdate isn't a tool to tell you the time, it's a tool to establish the offset between your clock and a remote clock. The timestamp that appears is just a log entry. If you want to use ntpdate you can put it in a cron job that gets called once per day or whatever. You may want to add the -s option so the log goes to syslog instead of stdout. This will work fine. >There was a discussion about time services on this list some time ago >and at that time I decided chrony should be used so I will try it >next. I don't want a service that keeps banging on the server. Once >a day seems reasonable to me. Can chrony be configured to check in >once a day. I don't expect the time to be more accurate than 30 >seconds. The computer does run 24/7 so the drift is in the software. chrony is also probably overkill for you. I'd suggest openntpd or systemd-timesyncd. They'll check more than once per day, but it's really not much traffic or a big deal. Or you can just stick with ntpdate. Mike Stone
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2018-08-09 16:50 +0200 |
| Message-ID | <wkUqe-4FO-9@gated-at.bofh.it> |
| In reply to | #198485 |
On Thursday 09 August 2018 10:19:46 Fred wrote: > Hi, > > Someone complained off list about the timestamp in my emails being > off. Being a hardware person I think hardware should work properly and > clocks should keep accurate time. So I installed ntpdate as suggested > but it is not active yet. And it only sets the clock once, at boot time. > Todays version of ntp(ntpd) handles that right well, my hardware clock is on grenwich and software on local, and both stay within 50 milliseconds of real time. > If I ask google what time it is in Mesa AZ. the response agrees > closely with an "atomic" clock I have. The computer clock is about 10 > min. fast. > > fred@ragnok:~$ /usr/sbin/ntpdate -q time.nist.gov > server 2610:20:6f96:96::4, stratum 1, offset -610.512368, delay > 0.09421 server 132.163.96.4, stratum 1, offset -610.509394, delay > 0.08899 9 Aug 06:51:15 ntpdate[13672]: step time server 132.163.96.4 > offset -610.509394 sec > > fred@ragnok:~$ date > Thu Aug 9 06:51:18 MST 2018 > > The time server is quite close to the computer clock. What causes the > discrepancy? The offset in the time server response is about 10 min. > The offset is measured from what to what and how is it measured? > As stated. ntp handles that by making small corrections so as to not disturb other time sensitive stuff on your computer. Thats another way of saying your 10 minute error may take it 4 hours to correct. The hdwe clock is set as part of the shutdown, so if you don't run 24/7, you don't start from square one the next time you powerup. And its so little cpu load you may not even find it with some of the monitoring facilities. Here, sorted on cpu usage, its about the 20th down the htop list. > Best regards, > Fred -- Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [standalone]
Page 3 of 3 — ← Prev page 1 2 [3]
Back to top | Article view | linux.debian.user
csiph-web