From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] systemd and journald
Date: Mon, 23 May 2016 10:07:09 +0200 [thread overview]
Message-ID: <20160523100709.3e2f0feb@itchy> (raw)
In-Reply-To: <20160522124140.GA3630@free.fr>
Hi!
Le Sun, 22 May 2016 14:41:40 +0200,
"Yann E. MORIN" <yann.morin.1998@free.fr> a ?crit :
> So, because our /var/log is a symlink to /tmp , the journal is
> correctly created
> in /tmp/journal/c30ad28b21d444ba9fff7fb25b5454b1/system.journal but
> since another filesystem is mounted over it later, it is no longer
> accessible, so journalctl does not find it.
>
> I'm not sure where to go forward rom there, but it looks like our
> skeleton is wrong when the init system is systemd.
I haven't played with a systemd-based setup for a while, but I used to fix this with a post-build script [1].
There was also a discussion some times ago about the need for a skeleton package per init system [2].
[1] https://github.com/elebihan/buildroot-ext-elb/blob/master/overlays/base-systemd/post-build.sh
[2] http://buildroot-busybox.2317881.n4.nabble.com/How-to-provide-one-default-skeleton-per-init-system-td72124.html
--
ELB
next prev parent reply other threads:[~2016-05-23 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-22 12:41 [Buildroot] systemd and journald Yann E. MORIN
2016-05-23 8:07 ` Eric Le Bihan [this message]
2016-05-24 19:38 ` Yann E. MORIN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160523100709.3e2f0feb@itchy \
--to=eric.le.bihan.dev@free.fr \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.