On 06.12.20 14:10, Jan Engelhardt wrote:
On Sunday 2020-12-06 12:48, Stefan Seyfried wrote: >> We noticed because SUSE's supportconfig tool took days to finish. It does a
"journalctl -b" to collect the journal... ;-)
So we created a service request and were told by SUSE professional support that it is unfixable, because the database design of the journal database just does not allow it to be read efficiently.
It speaks volumes that the professional support providers are not tempted to fix it.
Oh, they were trying and willing to fix it. IIRC actually the first response was "well, let's just fix journal". Then they looked closer at the problem and saw that this was not really possible.
"Got a problem? Come back when you have the logs. That is, if you ever do - *evil laughter*"
they did fix our problem -- by just adding the option to supportconfig to disable fetching of journal logs (important parts of /var/log/messages were collected anyway) I would not really want or expect SUSE to rewrite journald for a released product in a backwards incompatible way (since it is the "database format design" of the journald, it's basically impossible to fix in a backwards-compatible way). -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman