What are reasonable blockers for making journald the default logger in F19?

[Lennart Poettering]

On Wed, 17.10.12 11:04, Simo Sorce (simo at redhat.com) wrote:

> I was wondering if /var/log/messages could be turned into a named pipe
> to which journal start spitting out stuff in syslog format when someone
> tails it ?

Named pipes are single-reader streams. Also, for if they run full the
newest data is dropped, not the oldest, hence they are quite unsuitable
for a purpose like this.

I think it is a much better idea to make it easy for people to discover
the new tools (i.e. README file in /var/log) rather then trying to
emulate the old behaviour with pipes or cuse, which will necessarily be
incomplete and only working half-way. Especially given that people can
easily get their log files back, simply by installing syslog-ng/rsyslog.

> just a wild idea (and can be any other file name in /var/log as long as
> it is easily discoverable and doesn't cause issues to existing utilities
> that crawl /var/log), but I would strongly miss being able to tail logs
> with my pipeline that does coloring etc ...

(Side note: you get priority-based coloring in journalctl by default).

Lennart

-- 
Lennart Poettering - Red Hat, Inc.