Hi, On Wed, Dec 02, Eric Schirra wrote:
Hello Thorsten,
the first thing i do on a server is to disable systemd-journal and use logrotate.
logrotate does not write any logfiles, it moves them away if they get to big. So I assume, you disable systemd-journal and use a syslog implementation instead? Doesn't change anything on the picture, applications run via systemd service files still log to stdout/stderr and not in their log file.
How are you going to look for a bug in the log if you don't know exactly what to look for?
Sorry, I don't understand. I don't see a difference in filtering a file or the journalctl output.
So you're just looking for a pattern in the log.
That doesn't work with systemd.
Of course it works? I do that all the day.
This only works with text files.
journalctl output is pure ascii text?
And so systemd-journal is completely pointless for servers.
Please let it enable.
I don't want to disable anything, it is already disabled since a very long time. The output to log files is disabled in 99% of the packages who creates files or directories in /var/log I looked at. Seems like you mix up journald, syslogd, logrotate and applications creating their own log files. Thorsten
Regards
Eric
_______________________________________________ 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
-- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg)