From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Chrony-2.2 failing
Date: Mon, 7 Dec 2015 18:41:15 +0000 [thread overview]
Message-ID: <201512071841.16861.michaelkintzios@gmail.com> (raw)
In-Reply-To: <2951998.MWmNaIuBc5@wstn>
[-- Attachment #1: Type: Text/Plain, Size: 2116 bytes --]
On Friday 20 Nov 2015 09:24:52 Peter Humphrey wrote:
> On Thursday 19 Nov 2015 22:15:33 Marc Joliet wrote:
> > On Thursday 19 November 2015 10:49:08 Peter Humphrey wrote:
> > >Hello list,
> >
> > [...]
> >
> > >What's more, earlier versions had a decent man page and heavily
> > >commented chronyd.conf, but now the chrony.conf man page has been cut
> > >to a bare minimum and instead refers to a file chrony.txt "included in
> > >the distribution". I cannot find any such file after running ebuild
> > >$(equery w chrony) prepare.
> >
> > You've already gotten an answer regarding the man page, but with regards
> > to the configuration file in /etc, it looks like what you are looking for
> > is in the standard documentation path:
> >
> > % qlist chrony | grep doc/
> > /usr/share/doc/chrony-2.2/README
> > /usr/share/doc/chrony-2.2/NEWS
> > /usr/share/doc/chrony-2.2/FAQ
> > /usr/share/doc/chrony-2.2/chrony.conf.example1
> > /usr/share/doc/chrony-2.2/chrony.conf.example2
> > /usr/share/doc/chrony-2.2/chrony.conf.example3
> > /usr/share/doc/chrony-2.2/chrony.keys.example
> >
> > The *.example3 file is apparently the one that used to be copied to /etc.
> >
> > HTH
>
> Thanks for the ideas, gents.
I had another look at a laptop of mine and wondered if any of you gents had
added '/usr/local/bin/chronyc online/offline' in your laptop network scripts?
There's two issues with this laptop. First is that it is mostly used at home,
but occasionally may be used on the move, so an ntp server is not always at
hand. Second is that it can take up to 70 seconds to get an IP address from
the router, during which it will also have no access to the Internet.
This is my current config:
================================
server 0.uk.pool.ntp.org offline
server 1.uk.pool.ntp.org offline
server 2.uk.pool.ntp.org offline
server 3.uk.pool.ntp.org offline
maxupdateskew 100
driftfile /var/lib/chrony/drift
dumponexit
dumpdir /var/lib/chrony
makestep 1.0 3
rtcsync
rtcdevice /dev/rtc
================================
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-12-07 18:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 10:49 [gentoo-user] Chrony-2.2 failing Peter Humphrey
2015-11-19 17:06 ` Alexander Kapshuk
2015-11-19 17:17 ` Alan McKinnon
2015-11-20 10:22 ` Peter Humphrey
2015-11-20 11:03 ` Mick
2015-11-20 17:02 ` Peter Humphrey
2015-11-20 17:07 ` Alan McKinnon
2015-11-20 17:30 ` Mick
2015-11-21 9:59 ` Peter Humphrey
2015-11-24 15:24 ` Peter Humphrey
2015-11-25 17:05 ` Alan McKinnon
2015-11-26 10:39 ` Peter Humphrey
2015-11-26 13:00 ` Neil Bothwick
2015-11-26 14:00 ` Peter Humphrey
2015-11-26 15:04 ` Neil Bothwick
2015-11-26 15:12 ` Alan McKinnon
2015-11-27 9:33 ` Peter Humphrey
2015-11-20 19:39 ` brettrsears
2015-11-19 21:15 ` Marc Joliet
2015-11-20 9:24 ` Peter Humphrey
2015-12-07 18:41 ` Mick [this message]
2015-11-20 17:02 ` Dale
2015-11-20 17:06 ` Peter Humphrey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201512071841.16861.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox