Re: [chrony-dev] [PATCH v3] main: add -X to fall back if time is not adjustable

[FUSTE Emmanuel <emmanuel.fuste@xxxxxxxxxxxxxxx>]

Le 13/03/2018 à 19:57, Christian Ehrhardt a écrit :
>
>
> On Tue, Mar 13, 2018 at 5:54 PM, Bill Unruh <unruh@xxxxxxxxxxxxxx 
> <mailto:unruh@xxxxxxxxxxxxxx>> wrote:
>
>         [17:25] * cpaelzer fails at explaining it seems
>         [17:25] <cpaelzer> if you deploy chrony to a random system
>
>
>     If you have a random system and you have no idea whether or not
>     its clock is
>     good or a complete piece of merde, why would you want it acting as
>     a server
>     for anything? That is liable to cause mass confusion to the
>     clients who have
>     no idea whether or not to trust their server.
>
>
> Sorry, it was just a simplification to explain more easily.
> This is not an important detail to the discussion itself IMHO, but for 
> the sake of completeness, something like:
> s/random/a system where you have no means to check/ensure that either 
> on install time or for the lifetime of the system it will have the 
> capability to adjust the local clock. But even in case it's clock 
> would be a piece of merde let it get somewhat reliable time from 
> network sources and spread that locally to some peers to keep them in 
> sync among each other/
>
>
Reading more and more, I could not stay silent more time.
This way of thinking/doing things is completely mad.
Now we all need a GNSS receiver because people will happily spread crapy 
time even without knowing.
The -x is already highly questionable, but you're supposed to know what 
you do when using it.
Throwing things (what thing it is) away that "just seems to work" is a 
very very bad thing.
I'm sorry, but I still don't understand why/when this -X would be 
useful. And even if you give me a valid real case, it will only 
demonstrate that the real problem/needs are being tackled the wrong way.
We have a not politically correct dark humor expression for this in 
French: No hand, no chocolate.....

Emmanuel.