Re: [chrony-dev] [PATCH] main: imply -x if time can't be set

[Miroslav Lichvar <mlichvar@xxxxxxxxxx>]

On Thu, Mar 08, 2018 at 04:20:48PM +0100, Christian Ehrhardt wrote:
> On Thu, Mar 8, 2018 at 3:52 PM, Miroslav Lichvar <mlichvar@xxxxxxxxxx>
> wrote:
> > I'd rather keep it simple and avoid implementing an automatic fallback
> > in chrony.
> >
> 
> I understand the POV, but without even a default-off function for it I'm
> kind of forced to wrap a round it to be able to support the use-case in
> some way at least.

I still don't see a good use case for the option.

Is your intention to use in the default configuration? If not, what
difference will it make for the user to add -x or some other option
which enables -x?

If yes, will be the users that don't want chronyd to be started in
containers (but have it installed for some reason they cannot change)
happy with that?

> In general such a wrapper is inherently always slightly behind as not all
> downstreams share it, and I'd much more prefer coding something up that we
> share..

A script like that could be included the contrib directory if you
think others will find it useful.

> If that is a pre-nack to a patch adding a "-Please-fall-back-if-failing"
> then I don't have to waste the time writing it.
> So is there a chance at all to add such a switch in your opinion?

Not until I better understand the use case :).

-- 
Miroslav Lichvar

-- 
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.