* Claudio Freire <klaussfreire@gmail.com> [2012-09-19 18:14]:
On Wed, Sep 19, 2012 at 1:09 PM, Cristian Rodríguez <crrodriguez@opensuse.org> wrote:
Or export them to text .. peraphs to json which is much more easy to parse with automated tools...
Wasn't the idea of binary formats to make it easy for tools to parse?
How does that line "parse" then? Export to text to make the supposedly-very-machine-readable format easier to parse? Why not use text from the beginning then?
Please read the design document so you understand what we are talking about here.
Which one? This[0] one?
Doesn't say much.
[0] https://docs.google.com/document/pub?id=1IC9yOXj7j6cdLLxWEBAGRL6wl97tFxgjLUE...
It's also full of FUD about supposed limitations of syslog since it conveniently leaves out the advancements of modern syslog implementations like rsyslog or syslog-ng which are mostly on-par or superior in terms of features and functionality (well execept the log sealing feature but that seems inherently racy and is probably useless to those settings where log integrity is important). I haven't seen any hard evidence of higher performance of the "journal" compared to those syslog implementations. So the "journal's" raison d'être pretty much boild down to NIH. BTW, tha fact that you can't turn this completely useless stuff off is an execellent example of what is wrong with the new world order you're buying in when switching to systemd (rather than nebulous feeleings people have expressed here or the fact that the boot process and ui differ from sysvinit). -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org