Thanks Bill,
comments inline below.
Il 18/11/2015 20:40, Bill Unruh ha scritto:
Unfortunately something is seriously wrong:
I get consistently "506 Cannot talk to daemon" to each and all chronyc commands
I try (while being root).
Check that the chronyc and chronyd are the same versions.
T
Unfortunately something is seriously wrong:
I get consistently "506 Cannot talk to daemon" to each and all chronyc commands
I try (while being root).
Chronyd *is* running:
/ # ps ax | grep chro
510 root chronyd -r -s
602 root grep chro
... but I do not see the AF_LOCAL socket:
/ # ne
Note from the 2.2 manual page:
In 'chrony' versions before 2.2 the commands had to be authenticated
with a password and they were allowed from the internet, but that is no
longer supported.
You are running 1.31.
Teh whole socket etc was introduced as a security issue with the 2.x seri
On Thu, 19 Nov 2015, Mauro Condarelli wrote:
Thanks Bill,
now I am getting somewhere (at least chronyc seems to work).
I am still very confused, anyway.
I seem unable to match actual chrony behavior with manual
(http://chrony.tuxfamily.org/manual.html).
Well, things have changed between 1.31
sorry, my mistype. It is -a not -e
chronyc -a online
the -a tells chronyc to automatically read the password file /etc/chrony.keys
for the key to the password command of chronyc to allow it to run priviledged
commands.
On Thu, 19 Nov 2015, Mauro Condarelli wrote:
Hi,
I am very confused.
I se
On Thu, 19 Nov 2015, Mauro Condarelli wrote:
Hi Bill,
comments inline below.
Il 18/11/2015 21:04, Bill Unruh ha scritto:
On Wed, 18 Nov 2015, Mauro Condarelli wrote:
Thanks Bill,
comments inline below.
Il 18/11/2015 20:40, Bill Unruh ha scritto:
Unfortunately something is seriously wro
On Wed, Nov 18, 2015 at 01:39:40PM +0100, Mauro Condarelli wrote:
> >>4) wait for network to go up
> >>5) sync time THEN
> >>5.1) IF net time > sysclock THEN sysclock = net time
> >>5.2) IF net time < sysclock THEN slow sysclock TILL sysclock == net time
> >chronyd has only one step threshold for b
Thanks Miroslav,
comments are inline below.
Il 18/11/2015 11:33, Miroslav Lichvar ha scritto:
On Wed, Nov 18, 2015 at 12:04:07AM +0100, Mauro Condarelli wrote:
I have an embedded system (ARM9/Buildroot) that may or may not be connected to the
Internet (usually it is, but it should work also in
Actually the lack of /var/run/chrony would not seem to be the problem. I moved
/var/run/chrony.pid to Achrony.pid and chronyc started and displayed without
trouble.
William G. Unruh | Canadian Institute for| Tel: +1(604)822-3273
Physics&Astronomy | Advanced Research | Fax: +1(
On Wed, 18 Nov 2015, Mauro Condarelli wrote:
Thanks Bill,
comments inline below.
Il 18/11/2015 20:40, Bill Unruh ha scritto:
Unfortunately something is seriously wrong:
I get consistently "506 Cannot talk to daemon" to each and all chronyc
commands I try (while being root).
Check that th
On Tue, Nov 17, 2015 at 07:40:08PM -0500, James Knight wrote:
> server minpoll 4 maxpoll 6 iburst
> refclock SOCK /var/run/chrony.ttyS1.sock refid PPS prefer iburst
The iburst option is valid only for server/pool lines. With refclocks
the polling interval is constant. I'm wondering why chronyd do
Unfortunately something is seriously wrong:
I get consistently "506 Cannot talk to daemon" to each and all chronyc
commands I try (while being root).
Check that the chronyc and chronyd are the same versions.
Chronyd *is* running:
/ # ps ax | grep chro
510 root chronyd -r -s
602 root
On Wed, Nov 18, 2015 at 12:04:07AM +0100, Mauro Condarelli wrote:
> I have an embedded system (ARM9/Buildroot) that may or may not be connected
> to the Internet (usually it is, but it should work also in "detached" mode;
> connection may come up a long time after boot).
>
> I need to /ensure/ d
I have an embedded system (ARM9/Buildroot) that may or may not be connected to the
Internet (usually it is, but it should work also in "detached" mode; connection
may come up a long time after boot).
I need to /ensure/ dates are strictly monotonic; no "jump back" larger then one
second should
14 matches
Mail list logo
