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 to control the clock, i.e. its primary job, so it gives up. > b) there'll be a time-namespace. Actually a > good friend of mine from Red Hat is looking into this. :) This is very interesting and I'm curious how it will be implemented. Is there an upstream discussion? Some time ago, when I suggested that the CLOCK_MONOTONIC should be independent from CLOCK_REALTIME, the idea was rejected for performance reasons. Now, if I understand it correctly, each namespace would need to have its own clock running at a different frequency, which would separate the timers in the namespaces. -- Miroslav Lichvar -- To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.
