Re: [systemd-devel] [PATCH] journalctl: allow customizable output formats

2014-10-24 Thread Daniel P. Berrange
On Wed, Oct 08, 2014 at 11:53:38PM +0200, Lennart Poettering wrote: On Mon, 22.09.14 16:33, Daniel P. Berrange (berra...@redhat.com) wrote: The current '--output FORMAT' argument defines a number of common output formats, but there are some useful cases it does cover. In particular when

Re: [systemd-devel] [PATCH] journalctl: allow customizable output formats

2014-10-09 Thread Lennart Poettering
On Thu, 09.10.14 09:58, Daniel P. Berrange (berra...@redhat.com) wrote: Hmm, also, we already have a really bad formatter in place for the journal catalog files (which only replaces @foo@ by the value of field foo). We should probably use the same code for this new journalctl formatter

Re: [systemd-devel] [PATCH] journalctl: allow customizable output formats

2014-10-08 Thread Lennart Poettering
On Mon, 22.09.14 16:33, Daniel P. Berrange (berra...@redhat.com) wrote: The current '--output FORMAT' argument defines a number of common output formats, but there are some useful cases it does cover. In particular when reading application logs it is often desirable to display the code file

Re: [systemd-devel] [PATCH] journalctl: allow customizable output formats

2014-10-06 Thread Daniel P. Berrange
On Fri, Oct 03, 2014 at 02:13:51AM +0200, Zbigniew Jędrzejewski-Szmek wrote: On Mon, Sep 22, 2014 at 04:33:28PM +0100, Daniel P. Berrange wrote: The current '--output FORMAT' argument defines a number of common output formats, but there are some useful cases it does cover. In particular

Re: [systemd-devel] [PATCH] journalctl: allow customizable output formats

2014-10-02 Thread Zbigniew Jędrzejewski-Szmek
On Mon, Sep 22, 2014 at 04:33:28PM +0100, Daniel P. Berrange wrote: The current '--output FORMAT' argument defines a number of common output formats, but there are some useful cases it does cover. In particular when reading application logs it is often desirable to display the code file name,

Re: [systemd-devel] [PATCH] journalctl: allow customizable output formats

2014-09-23 Thread Daniel P. Berrange
On Mon, Sep 22, 2014 at 12:43:28PM -0400, Daurnimator wrote: On 22 September 2014 11:33, Daniel P. Berrange berra...@redhat.com wrote: The current '--output FORMAT' argument defines a number of common output formats, but there are some useful cases it does cover. In particular when

Re: [systemd-devel] [PATCH] journalctl: allow customizable output formats

2014-09-23 Thread Kashyap Chamarthy
[Strangely, this thread up in my inbox rather than my systemd Maildir.] On Mon, Sep 22, 2014 at 12:43:28PM -0400, Daurnimator wrote: On 22 September 2014 11:33, Daniel P. Berrange berra...@redhat.com wrote: The current '--output FORMAT' argument defines a number of common output formats,

[systemd-devel] [PATCH] journalctl: allow customizable output formats

2014-09-22 Thread Daniel P. Berrange
The current '--output FORMAT' argument defines a number of common output formats, but there are some useful cases it does cover. In particular when reading application logs it is often desirable to display the code file name, line number and function name. Rather than defining yet more fixed

Re: [systemd-devel] [PATCH] journalctl: allow customizable output formats

2014-09-22 Thread Daurnimator
On 22 September 2014 11:33, Daniel P. Berrange berra...@redhat.com wrote: The current '--output FORMAT' argument defines a number of common output formats, but there are some useful cases it does cover. In particular when reading application logs it is often desirable to display the code file

Re: [systemd-devel] [PATCH] journalctl: allow customizable output formats

2014-09-22 Thread Ivan Shapovalov
On Monday 22 September 2014 at 12:43:28, Daurnimator wrote: On 22 September 2014 11:33, Daniel P. Berrange berra...@redhat.com wrote: The current '--output FORMAT' argument defines a number of common output formats, but there are some useful cases it does cover. In particular when