The Wanderer <wande...@fastmail.fm> writes: > In my case: because I want to be able to read them conveniently at a > glance, without requiring the presence of a functioning specialized tool > for doing so. As the UNIX Philosophy puts it, "text streams ... [are] a > universal interface".
All the folks who are upset about the journal are aware, I hope, that, as configured in the current systemd packages in Debian at least (I haven't tried a generic upstream install), all journal messages are forwarded directly to syslog, right? All the text files that you are looking for still exist in the same form they always have. The journal serves as a mechanism for routing some things into syslog that wouldn't otherwise go there (such as stderr output from daemons) and as a data store for some nice but entirely optional systemd debugging features, such as "show me all the output logged from this particular daemon but not any of the others." It doesn't replace syslog. I am in wholehearted agreement with the people who want all their log messages to go into syslog so that they can be processed, routed, and so forth just as they are today. I, and I suspect many others who like systemd, would be quite unhappy if that didn't happen. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87y51hr1lf....@windlord.stanford.edu
