To no one in particular here -- Journald has, for years now, been a standard with overwhelming adoption and precedent, and logging patterns that rely on other mechanisms like logrotate should be viewed as legacy in 2020 -- and generally are by most users. The SystemV fight was lost. It's done. it's over. It's no longer time to adopt systemd. That time has passed. Pursuing legacy logging patterns over personal preference is generally bad for package continuity. Maybe consider moving the logrotate options as annexes in a secondary repository or something. This would be a great place to also move packages maintained by folks who don't think systemd is a base integration requirement until they either drop package or modernize. If you go this no-systemd route discussed here you'll eventually be doing it alone. -C On Sun, Dec 6, 2020 at 5:16 AM Stefan Seyfried < stefan.seyfried@googlemail.com> wrote:
On 02.12.20 17:10, Thorsten Kukuk wrote:
Sorry, I don't understand. I don't see a difference in filtering a file or the journalctl output.
Speed.
Taking 8 hours to just provide the logs of this boot from the non-persistent ram disk journal(!!) on a pretty big server is a no-no.
Just look at the customers support request that caused supportconfig to grow a flag to disable or trim journal collection :-)
Of course it works? I do that all the day.
You seem to only have tiny systems or not really much to do ;-)
journalctl output is pure ascii text?
but it is slllooooooooooooooooooooooooooooooowwwwwwwwwwwwwwwwwwwwwww. -- Stefan Seyfried
"For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman _______________________________________________ openSUSE Packaging mailing list -- packaging@lists.opensuse.org To unsubscribe, email packaging-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/packaging@lists.opensuse.org