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

On Wed, Mar 14, 2018 at 11:42 AM, Miroslav Lichvar wrote: > On Wed, Mar 14, 2018 at 11:16:10AM +0100, Christian Ehrhardt wrote: > > On Wed, Mar 14, 2018 at 11:01 AM, Miroslav Lichvar > > wrote: > > > At this time, I'd be interested in including only in

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

On Wed, Mar 14, 2018 at 11:16:10AM +0100, Christian Ehrhardt wrote: > On Wed, Mar 14, 2018 at 11:01 AM, Miroslav Lichvar > wrote: > > At this time, I'd be interested in including only in the first one. We > > can reconsider the other two later if you are still interested. > >

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

On Wed, Mar 14, 2018 at 11:01 AM, Miroslav Lichvar wrote: > On Tue, Mar 13, 2018 at 10:45:56AM +0100, Chr?stian Ehrhardt wrote: > > doc/chronyd.adoc | 7 +++ > > examples/chronyd.service | 1 - > > main.c | 10 +++--- > > sys.c

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

Few more thoughts about this. On Tue, Mar 13, 2018 at 05:40:56PM +0100, Christian Ehrhardt wrote: > [17:28] We have two cases how this can run > [17:28] 1. if this runs on a Host that can set time, it has to > be in sync with what it serves time to - so it needs to set local time > [17:28] so

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

Le 13/03/2018 à 19:57, Christian Ehrhardt a écrit : > > > On Tue, Mar 13, 2018 at 5:54 PM, Bill Unruh > wrote: > > [17:25] * cpaelzer fails at explaining it seems > [17:25] if you deploy chrony to a random system > > > If

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

On Tue, Mar 13, 2018 at 5:54 PM, Bill Unruh wrote: > [17:25] * cpaelzer fails at explaining it seems >> [17:25] 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

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

[17:25] * cpaelzer fails at explaining it seems [17:25] 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

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

On Tue, Mar 13, 2018 at 5:24 PM, Christian Ehrhardt < christian.ehrha...@canonical.com> wrote: > > > On Tue, Mar 13, 2018 at 4:02 PM, Christian Ehrhardt < > christian.ehrha...@canonical.com> wrote: > >> >> >> On Tue, Mar 13, 2018 at 2:50 PM, Miroslav Lichvar >> wrote: >> >>>

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

On Tue, Mar 13, 2018 at 4:02 PM, Christian Ehrhardt < christian.ehrha...@canonical.com> wrote: > > > On Tue, Mar 13, 2018 at 2:50 PM, Miroslav Lichvar > wrote: > >> On Tue, Mar 13, 2018 at 12:17:41PM +0100, Christian Ehrhardt wrote: >> > The important part is the lack of

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

On Tue, Mar 13, 2018 at 2:50 PM, Miroslav Lichvar wrote: > On Tue, Mar 13, 2018 at 12:17:41PM +0100, Christian Ehrhardt wrote: > > The important part is the lack of knowledge of the target systems > > capabilities. > > They are: > > - not detectable by some install paths,

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

On Tue, Mar 13, 2018 at 12:17:41PM +0100, Christian Ehrhardt wrote: > The important part is the lack of knowledge of the target systems > capabilities. > They are: > - not detectable by some install paths, for example > - install in VM with behavior A onto phys disk but reboot host into said >

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

On Tue, Mar 13, 2018 at 11:29 AM, Miroslav Lichvar wrote: > On Tue, Mar 13, 2018 at 10:45:56AM +0100, Christian Ehrhardt wrote: > > In unprivileged containers even after e8096330 "sys_linux: don't keep > > CAP_SYS_TIME with -x option" default installations > > will still run

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

In unprivileged containers even after e8096330 "sys_linux: don't keep CAP_SYS_TIME with -x option" default installations will still run without an explicit -x being set and therefore fail by missing CAP_SYS_TIME. In some use cases users want the NTP server service to "just work" which in a