3 ms·
The logging and monitoring tools are /worse/ than in a BSD or SysV init situation. Journald, as opposed to rsyslog and syslog-ng, can't talk to other systems in
by Sanddancer 12y ago
The logging and monitoring tools are /worse/ than in a BSD or SysV init situation. Journald, as opposed to rsyslog and syslog-ng, can't talk to other systems in anywhere near a sane manner, can't connect to databases, has no ability to filter and direct messages, etc. On top of that, it makes core dumps require root privileges to analyze them, making user level development and debugging more difficult. Systemd has a heavy, heavy stink of someone from the desktop realm coming in with no knowledge of what tools sysadmins already use, and screwing everything up in the process.
- kiyoto 12y ago>The logging and monitoring tools are /worse/ than in a BSD or SysV init situation. Journald, as opposed to rsyslog and syslog-ng I have to agree. I am one of the main people to support Fluentd (an open source log collector https://www.fluentd.org https://www.fluentd.org), and a lot of people do forward rsyslog/syslog-ng to Fluentd for further processing/analytics. We've been trying to figure out a way to do the same with journald, and while it does seem possible, it will require a ton more work.
- keithpeter 12y agoRedhat employ the core systemd developers, and RHEL is mainly a server product. Senior Redhat people must understand the issues and have decided to go with this system for a reason. I'm just wondering what the reason was! One of them has just jumped ship to Google mind you!