5 ms·
Because in BSD, that consolidation and standardization is optional by design, with everything given knobs to disable it. For example, I don't like FreeBSD's sys
by Sanddancer 11y ago
Because in BSD, that consolidation and standardization is optional by design, with everything given knobs to disable it. For example, I don't like FreeBSD's syslog -- I prefer syslog-ng. Therefore, I have the following in my /etc/rc.conf
#use syslog-ng instead of the built-in syslog
syslog_ng_enable="YES"
syslogd_enable="NO"
and as such, I have my own syslog running. Systemd, on the other hand, disabling their syslog is simply not an option, as is the case with so many components that it encompasses.
The BSD's philosophy is indeed to have a cohesive system, however, they recognize that they don't always have the best defaults for every situation, and thus make it easy, and supportable, to set options the way you want.
- jmhain 11y ago> Systemd, on the other hand, disabling their syslog is simply not an option You can set Storage=none and ForwardToSyslog=yes in /etc/systemd/journald.conf [0]. [0] https://wiki.archlinux.org/index.php/Syslog-ng#syslog-ng_and_systemd_journal https://wiki.archlinux.org/index.php/Syslog-ng#syslog-ng_and...
- Sanddancer 11y agoThat's not disabling journald, that's disabling journald writing messages. It's still receiving every byte sent to the system log, it's still in memory, and otherwise still running.
- cthalupa 11y agoThe journal still takes over /proc/kmsg. You're relying on journald working properly, and you cannot bypass it. Forwarding things on from journald is not the same as disabling it completely. (This sort of inability to make decisions about what tools you use for your system is one of the complaints about systemd)