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

On Fri, Mar 9, 2018 at 8:18 AM, Miroslav Lichvar wrote: > On Thu, Mar 08, 2018 at 06:09:00PM +0100, Miroslav Lichvar wrote: > > On Thu, Mar 08, 2018 at 05:08:16PM +0100, Christian Ehrhardt wrote: > > > 1. the option would not be default on, so "normal" users/installations >

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

On Thu, Mar 08, 2018 at 06:09:00PM +0100, Miroslav Lichvar wrote: > On Thu, Mar 08, 2018 at 05:08:16PM +0100, Christian Ehrhardt wrote: > > 1. the option would not be default on, so "normal" users/installations > > would not be affected > > 2. cases that want the fallback behavior, but are unable

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

On Thu, Mar 08, 2018 at 05:08:16PM +0100, Christian Ehrhardt wrote: > 1. the option would not be default on, so "normal" users/installations > would not be affected > 2. cases that want the fallback behavior, but are unable to probe/detect at > the time: >- so they can not decide to use normal

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

... concept of a time namespace in the future. For most non-namespaced resources applications that are expected to run in user namespaces (systemd, lxc, etc.) follow the concept of "seek forgiveness, not permission" meaning one should usually check whether an operation is That, for a program,

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

On Thu, Mar 08, 2018 at 05:15:44PM +0100, Christian Brauner wrote: > Now, I think it would make sense for chrony to be a "seek > forgiveness, not permission" application since a) it is expected to be > run in user namespaces and I think chronyd is already doing that, except there is no other way

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

On Thu, Mar 08, 2018 at 03:59:30PM +0100, Christian Ehrhardt wrote: > On Thu, Mar 8, 2018 at 3:52 PM, Miroslav Lichvar > wrote: > > > On Thu, Mar 08, 2018 at 03:15:36PM +0100, Christian Ehrhardt wrote: > > > On Thu, Mar 8, 2018 at 1:49 PM, Miroslav Lichvar

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

On Thu, Mar 8, 2018 at 4:34 PM, Miroslav Lichvar wrote: > On Thu, Mar 08, 2018 at 04:20:48PM +0100, Christian Ehrhardt wrote: > > On Thu, Mar 8, 2018 at 3:52 PM, Miroslav Lichvar > > wrote: > > > I'd rather keep it simple and avoid implementing an

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

On Thu, Mar 8, 2018 at 3:52 PM, Miroslav Lichvar wrote: > On Thu, Mar 08, 2018 at 03:15:36PM +0100, Christian Ehrhardt wrote: > > On Thu, Mar 8, 2018 at 1:49 PM, Miroslav Lichvar > > > But this is what users expect in most cases, right? If an NTP > > >

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

On Thu, Mar 08, 2018 at 03:15:36PM +0100, Christian Ehrhardt wrote: > On Thu, Mar 8, 2018 at 1:49 PM, Miroslav Lichvar > > But this is what users expect in most cases, right? If an NTP > > client/server is installed and enabled in a container, it's usually > > not intended,

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

On Thu, Mar 8, 2018 at 1:49 PM, Miroslav Lichvar wrote: > On Thu, Mar 08, 2018 at 12:21:16PM +0100, Christian Ehrhardt wrote: > > 1. if you are in a container you very likely can't set the time. > > Installing chrony there would silently not start the chrony service >

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

On Thu, Mar 08, 2018 at 12:21:16PM +0100, Christian Ehrhardt wrote: > 1. if you are in a container you very likely can't set the time. > Installing chrony there would silently not start the chrony service for > lacking CAP_SYS_TIME. > - You now installed chrony got no error/warning, but it

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

On Thu, Mar 8, 2018 at 10:14 AM, Miroslav Lichvar wrote: > On Wed, Mar 07, 2018 at 04:43:20PM +0100, Christian Ehrhardt wrote: > > I thought that having the server portion work by default would be very > nice > > to user. > > Are there any users that want to run an NTP

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

On Wed, Mar 07, 2018 at 04:43:20PM +0100, Christian Ehrhardt wrote: > I thought that having the server portion work by default would be very nice > to user. Are there any users that want to run an NTP server knowing that the clock is not synchronized by something else, but not care if it will be