On Tue, 09.10.12 18:37, Richard W.M. Jones (rjones(a)redhat.com) wrote:
On Tue, Oct 09, 2012 at 07:34:50PM +0200, drago01 wrote:
> On Tue, Oct 9, 2012 at 7:30 PM, Richard W.M. Jones <rjones(a)redhat.com> wrote:
> > On Tue, Oct 09, 2012 at 04:16:16PM +0200, Lennart Poettering wrote:
> >> 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>
> >
> > What is <pathtothejournalfiles> in an actual system?
>
> From the man page:
>
> By default the journal stores log data in /run/log/journal/. Since
> /run/ is volatile log data is lost at reboot.
WTF?
> To make the data
> persistent it is sufficient to create /var/log/journal/ where
> systemd-journald will then store the data.
I'm assuming this directory will be created, before /var/log/messages
disappears.
Yes, of course.
Lennart
--
Lennart Poettering - Red Hat, Inc.