[opensuse-factory] /etc/chrony.d/pool.conf -> 100% CPU
HI! 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. Ciao, Michael. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
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. Ciao, Michael. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, 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. I wonder about the CPU use though, that shouldn't happen and needs to be fixed. Do you know what combination of options causes this?. Please file a bug report. Cheers, Fabian
Ciao, Michael.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Citeren Fabian Vogt <fvogt@suse.de>:
Hi,
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 :-)
This is probably just semantics, but for a previously installed chronyd it is unexpected that an update will suddenly add a new NTP pool. I understand it makes sense to add the pool configuration in a separate subpackage, to allow to push changes for installations where nobody ever bothers changing that. I would like to have seen an 'opt in' rather than the 'opt out' we have now. This could also have been accomplished by adding the two different flavors (SUSE and openSUSE) pools in separate files and explicitly including one of them in /etc/chrony.conf upon first installation, rather than through the blanket include /etc/chrony.d/*.conf directive. By doing so, existing installations (which probably already have a working NTP source configuration) would not have been affected, while new installations would have a working configuration out-of-the-box.
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.
I wonder about the CPU use though, that shouldn't happen and needs to be fixed. Do you know what combination of options causes this?. Please file a bug report.
Cheers, Fabian
Ciao, Michael.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
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
On 16/06/2020 13.17, Michael Ströder wrote:
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.
There is a little known trick with zypper, where you can request install and uninstall in one operation by prefixing uninstalls with minus: zypper -n in chrony-pool-empty -chrony-pool-openSUSE if that is what you meant. The other way is zypper -n in --force-resolution chrony-pool-empty -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Arjen de Korte -
Bernhard M. Wiedemann -
Fabian Vogt -
Michael Ströder