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 03/07/2018 07:43 AM, Christian Ehrhardt wrote:
So the question is, is this "so bad" that we should not fall back by
default.
Or is this a minor degradation and the comfort for the NTP server component
to just work outweighs the concern.


Doing a fallback without some kind of notice is just plain wrong. Being silent is just wrong.

Now, if you were to make a local mail to root that you have to fall back, that would be sufficient enough to eliminate the "astonishment factor."

how about -x1 for saying "die on failure", and -x or -x0 for "fallback on failure"? Or some other option?

--
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.


Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/