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 reading application logs it > > is often desirable to display the code file name, line number > > and function name. Rather than defining yet more fixed output > > formats, this patch introduces user defined output formats. > > > > The format string is an arbitrary string which contains a > > mixture of literal text and variable subsistitions. Each > > variable name corresponds to a journal field name. A variable > > name can be optionally followed by a data type, and in the > > case of string types, a length limit. > > > > As an opposing point of view, I've been accomplishing this by piping output > through a script that parses and displays JSON. > I rather this style of composability than passing format strings to > journalctl itself.
I think that using dedicated ad-hoc JSON parser for customizing output is an overkill. For that matter, Git has support for custom output format in its "log" command, and I've found it useful many times. -- Ivan Shapovalov / intelfx /
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
