| Re: [chrony-users] leapsectz and phc refclock offset |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] leapsectz and phc refclock offset
- From: Chris Perl <cperl@xxxxxxxxxxxxxx>
- Date: Mon, 2 Oct 2017 09:03:57 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=janestreet.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=C/NXqJnLCNRuSHK/0d8vlmRbcpQjmxLwVHT0KxFpVyI=; b=d2LT8I/IhkgccmRo/EdM3ws0QURPCu5sG9HTjCnqToSnoRfJkMrln1eywarYUHCG1H p9T+5s8/Ieyg5dGgvVm+vJZ5F3KssTANygZhkiKmrePKEAjbQZqNtJok4E3EfCk9+M5u D9LYi8EFYMqZehzmeKX243ef92fP0cQbVvV/Q=
On Thu, Sep 28, 2017 at 11:40 AM, Chris Perl <cperl@xxxxxxxxxxxxxx> wrote:
> This works to some extent, although not as robustly as I would have
> hoped.
Thinking about this a bit more, I was wondering what you would think
about having some manual way to tell chronyd that a given refclock is
currently in a bad state and should not be used (e.g. some chronyc
command to do so). I thought perhaps using something like `offline'
might just work, but I don't think I'm able to offline a refclock (or,
at least my first few attempts failed with errors about trying to
resolve the name).
If I had such a command, I could write my own (simple) monitoring
daemon that could decide if the PHC refclock was in a good state or
not and then update chronyd with that information.
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.