Am 19.09.2012 17:49, schrieb Cristian Rodríguez:
El 19/09/12 11:20, Claudio Freire escribió:
On Wed, Sep 19, 2012 at 7:26 AM, Ruediger Meier <sweet_f_a@gmx.de> wrote:
Unfortunately you can do this only on machines where journalctl is installed/available. I assume that you can't read the journald logs on most existing systems.
Just a matter of building journalctl from source I'd imagine, as would be the case if you were missing grep.
Or export them to text .. peraphs to json which is much more easy to parse with automated tools...
Unfortunately, there is no tool to read or export the BLOB put onto my disk and fragmenting my filesystem like hell, see https://bugzilla.novell.com/817778 Yay. Never had that with text logs. Maybe they were missing a few lines after a crash, or they had some kB of binary garbage interspersed, but I could always read them.
I happen to agree that the binary format is unnecessary,
Ok, then how you implement all those features mentioned in the design document to work fast ?
I give a sh*t on that design document, as long as I can not read my logs, it is the end of the month and they would be very useful to do my accounting. Fun facts about sytemd-journal: * it logs to a binary database * it can not filter out the user session logs from the system logs * if the database is broken, i tells you (journalctl --verify) * but it can not repair or recover it * even if the database is not broken, it can not read it (bnc#817778) * fills the disk way beyound its configured limits (bnc#817780) ...well, only "fun" if you have a strange definition of "fun". -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org