On 6/16/20 12:37 PM, Fabian Vogt wrote:
Am Dienstag, 16. Juni 2020, 07:00:48 CEST schrieb Michael Ströder:
On 6/16/20 6:37 AM, Michael Ströder wrote:
Why is package chrony-pool-openSUSE required by package chrony?
It always recreates the file /etc/chrony.d/pool.conf which makes my self-configured chronyd eat all the CPU.
I've discovered and installed chrony-pool-empty but still such a change should not be enforced.
As you found out by yourself, it's actually not enforced :-)
It's expected that a plain install of chrony works OOTB, including having a server entry. YaST will make use of that file to get the default settings soon as well AFAIK.
But was strikes me that it required interactive use of zypper to install chrony-pool-empty for uninstalling chrony-pool-openSUSE. I really hate this enforced pseudo config management.
I wonder about the CPU use though, that shouldn't happen and needs to be fixed.
https://bugzilla.opensuse.org/show_bug.cgi?id=1172978 Ciao, Michael. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org