On Tue, 09.10.12 09:38, Chris Adams (cmadams(a)hiwaay.net) wrote:
Once upon a time, Lennart Poettering <mzerqung(a)0pointer.de>
said:
> On Tue, 09.10.12 09:09, Chris Adams (cmadams(a)hiwaay.net) wrote:
> > Once upon a time, Lennart Poettering <mzerqung(a)0pointer.de> said:
> > > If people want some pixel-perfect copy of the traditional
> > > /var/log/messages, then they should just run "journalctl"
without any
> > > args. It's much better than /var/log/messages:
> >
> > How do you read this log when the system is not running (e.g. mounting
> > filesystems of a drive on another system, running from a rescue image,
> > etc.)?
>
> journalctl -D <pathtothejournalfiles>
And just what is the <pathtothejournalfiles> (relative to system /)?
The path where the journal files resides or where the per-machine
subdirs reside. More specifically "-D/var/log/journal/<machine-id>" if
you
only want to see the logs from that one machine. Or "-D/var/log/journal" if
you want to see the logs from all per-machine dirs in there. The files
will be interleaved as appropriate in that case. The machine ID is the
contents of /etc/machine-id.
Lennart
--
Lennart Poettering - Red Hat, Inc.