FYI - this is a first pass to putting the bootcharts into the journal,
exactly as coredump does. Ultimately, I will probably make bootcharts
not go to disk other than the journal by default.

A single one-liner can be used to get the latest bootchart automatically:

$ journalctl -b MESSAGE_ID=9f26aa562cf440c2b16c773d0479b518
--field=BOOTCHART > bootchart.svg

Auke


---------- Forwarded message ----------
From: Auke-Jan Kok <a...@kemper.freedesktop.org>
Date: Mon, Apr 15, 2013 at 4:29 PM
Subject: [systemd-commits] Makefile.am src/bootchart
To: systemd-comm...@lists.freedesktop.org


 Makefile.am               |    3 +-
 src/bootchart/bootchart.c |   53 ++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 55 insertions(+), 1 deletion(-)

New commits:
commit c4d58b0b6d238b955ece39a9dd9d3ca84b3408f3
Author: Auke Kok <auke-jan.h....@intel.com>
Date:   Mon Apr 15 16:23:42 2013 -0700

    bootchart: put the bootchart into the journal.

    This bit of code is mostly stolen from coredump.c. We construct
    a simple journal message and append the bootchart file in the
    journal automatically.

    You can extract the latest bootchart from the current boot with
    something like:

    $ journalctl -b MESSAGE_ID=9f26aa562cf440c2b16c773d0479b518
--field=BOOTCHART

    which prints it to stdout.

    None of the other logic is touched. The journal entry is created
    even if bootchart was run manually, which is probably wrong.
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Reply via email to