OpenSuSE and logging: no more syslogd; journald is default, you can use rsyslog or syslog-NG as syslogd replacements
Posted by jpluimers on 2016/11/15
In the 1990s and early 2000s I did a lot of Unix-Like (Minix, SunOS, HP-UX, Xenox) and later Linux (mostly RedHat and SuSE) work. The internet and Linux weren’t as big as they are now and old stuff was still in use including syslogd.
So recently wanting to do more on the Linux side of things using OpenSuSE (as 15+ years ago, I spent most of my time with SuSE Linux) and assumed logging was still done using syslogd like Mac OS X does.
Boy, I was wrong. Like the internet and lots of other things, logging on OpenSuSE has fragmented in at least these three categories of which two syslog implementations (but syslogd is deprecated and – according to the URC #SUSE Channel – unmaintained):
- journald (installed by default on my Tumbleweed text-only systems)
- rsyslog (which is supposed to be default on modern OpenSuSE installs but somehow isn’t on my Tumbleweed but is on 13.1 and 13.2)
- proprietary logging (of many applications in
/var/loglike named, apache, etc)
There seems to be heated debates on what to use when, so I’ll try to stick with the defaults as much as possible.
A few things I need to sort out:
- where is journald persisted?
- how can journald being rotated?
- Seems a setting too: systemd – journald Settings likey need your attention
- what to do with packages that require one form of syslog or the other?
- not sure yet
- can I direct journald to a syslog implementation?
- should work if you install rsyslog or syslog-ng next to journald: syslog not installed by default in openSUSE 13.2?
- how does this apply to other distros?
- not sure yet