Ok thanks, I tried with 'local" before and got very bad results, did some
digging and turns out that was because I was having the same driftfile on
both instance (probably the parameter isn't necessary on the server
config), it's better now.
I specified a custom sock as bindcmdaddress for each instance
(/var/run/chrony/chronyd_1.sock and /var/run/chrony/chronyd_1.sock) and a
custom cmdport for sthe server instance.
I can get chronyc to work with both instance, however ntpdata is not
working on neitheir of them, i get "501 Not authorised", any idea ?
2017-09-11 11:07 GMT+02:00 Miroslav Lichvar <mlich...@redhat.com>:
> On Fri, Sep 01, 2017 at 07:00:08PM +0200, Thibaut BEYLER wrote:
> > I already have a secondary interface & addresses configured on my
> > so I was thinking to use it for the second instance instead of using a
> > non-standard port (which my monitoring software doesn't support)
> > But how can I configure the server instance it to serve the local time ?
> > I don't put any server directive it won't serve ntp, and if i put a
> > directive it will serve that time..
> There is the "local" directive for that. It allows chronyd to serve
> the local system time, even if it's not synchronized to anything.
> Miroslav Lichvar
> To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
> with "unsubscribe" in the subject.
> For help email chrony-users-requ...@chrony.tuxfamily.org
> with "help" in the subject.
> Trouble? Email listmas...@chrony.tuxfamily.org.