| Re: [chrony-dev] [PATCH] main: imply -x if time can't be set |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
On Fri, Mar 09, 2018 at 08:36:36AM +0100, Christian Ehrhardt wrote:
> On Fri, Mar 9, 2018 at 8:18 AM, Miroslav Lichvar <mlichvar@xxxxxxxxxx>
> wrote:
> > I still don't see the use case for the fallback. If applications
> > running in the container are ok with chronyd not controlling the
> > clock, why not always use -x there? At least it will be less likely to
> > hit the case where two things are trying to control the clock.
> >
>
> The use case IMHO is for anyone that wants to opt-in to a "just have ntp
> serving work at any quality" behavior.
I'd say the -x option already does that. If they don't care about the
system clock, it's ok to use -x even if chronyd would be able to
control it.
> That would fulfil the needs of the reporter of my bug at least - so there
> is a valid use case.