You are not logged in.
Pages: 1
Which is the best way to obtain plain text logs like back in the syslog era?
I haven't find a lot of info searching around (both forum and Google), just that for arch these 2 seem to be the available choices:
https://wiki.archlinux.org/index.php/rsyslog
https://wiki.archlinux.org/index.php/Syslog-ng
But I don't understand:
1) What makes rsyslog better than syslog-ng.
2) If I can use rsyslog to read other stuff than only kernel messages.*
* As reported from the wiki: "Note: rsyslog reads from /proc/kmsg. This means that subsequent reads from that file (either the user or a syslog daemon) will not read "old" logs from that file anymore. journald is not affected as it reads from /dev/kmsg which allows multiple readers."
Instead journalctl read various level https://wiki.archlinux.org/index.php/Systemd#Journal
Offline
I know nothing about rsyslog, but have used syslog-ng for years.
syslog-ng can connect sources, filters and destinations in many ways.
My main system rarely boots into systemd, so (even if i wanted to) i can't use journald.
Setting up syslog-ng to maintain logs for multiple init system for all inits was not hard, can rsyslog do the same ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Which is the best way to obtain plain text logs like back in the syslog era?
Why do you want plain text logs?
The systemd journal files can be read directly with strings(1), if that helps.
Jin, Jîyan, Azadî
Offline
Pages: 1