On Thu, Sep 20, 2012 at 4:51 PM, Peter Czanik <pczanik@fang.fa.gau.hu> wrote:
Before we all end up in flames, a hopefully not too biased view from syslog-ng upstream :-)
Yep, sorry about that. I was prodded and reacted before I noticed.
First of all, systemd journal is a perfect solution for about 90%+ of openSUSE users, which have stand alone workstations and don't care at all about logging. They don't need rsyslog or syslog-ng. The journal collects logs under /var/log/journal into some binary files. By default it does not take more than 5% of available disk space, so logs can't fill up the partition accidentally. It's very limited, but user friendly. Actually I don't really understand, why syslog is still installed on openSUSE (ArchLinux removed syslog from systemd based installations to avoid dual logging...), but this is a different questions...
Strangely enough, I agree. I complain about the binary log because it's unnecessary complexity and obscurity, but the fact that workstation users rarely need to bother reading the logs kind of dilutes the effects of all that, and the fact that syslog is still functional in openSUSE is a very very good thing for those that do. Having it run, by default, in tandem with journal was, AFAIK, a transitional measure. Because all init stuff goes into the journal, and users new to systemd won't know where to find all those messages and be unable to fix boot problems. Now, systemd is fixing the tty "bug" that made it not show those messages to the console, meaning users will *see* what's wrong, and syslog will cease to be useful in the default installation. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org