Hi Jonas, I have a comment, and a question. On Sun, Nov 17, 2013 at 03:46:55PM +0200, Joonas Sarajärvi wrote: > 2013/11/17 Frantisek Hanzlik <franta@xxxxxxxxxxx>: > > > > It was mean mainly from administrator view. When things go bad, > > machine HW/SW fail or any other disasters occurs, logs are very > > valuable. And I'm confident that binary logs are too weak in this > > situation. Text logs are useful even if log file is damaged or ends > > with fragments and can be easy readable with lot of tools. Binary > > logs, by contrast, may be useless when log file is damaged or I > > haven't this one unique utility for reading them. And my experiences > > with systems where binary logs are implemented says clearly that > > binary logs is bad idea. > > Second, it is question when tight integration of systemd and logging > > services has any benefits - there is number of situation (logging > > over network, for example) which speaks for separate logging service. > > The journald log format is documented at least to some extent [1], and > there exists free software for reading the log. To me, it sounds like > way more accessible than if it was a binary data format of a typical > proprietary tool. For example, booting any Fedora live image should > suffice if you need to read the journal of a system that uses journald > and happens to become unbootable. I am sure you (and everyone else on the list) will agree, tools for viewing plain text (cat, more, less, <favourite editor>) outnumber and are available on every platform compared to any specialised tool. Even if a format is open, it still needs tools that support it. I would not count on having a gui when my system crashes. Sometimes the only access you have to a crashed system is the recovery prompt. [...chomp...chomp...chomp...] > At least for my needs, the journal has been way more convenient to use > than rsyslog. It is much nicer to read logs when journalctl e.g. > combines the older rotated logs with the latest ones. Also, it easily > allows me to easily specify that I want just the logs of this month or > of just this one boot, or of just some specific service. I have been very frustrated with journalctl. The manual page is very unhelpful in that regard. For example the other day, I wanted to investigate why my laptop shutdown suddenly (I think it was overheating), but there was no reasonable way for me to filter the cpu specific messages. Could you give some pointers how I can do that? I would be very grateful. Thanks, PS: I'm no sysadmin, just a regular *nix user who prefers the command line. -- Suvayu Open source is the future. It sets us free. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
