From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Le Bihan Date: Mon, 23 May 2016 10:07:09 +0200 Subject: [Buildroot] systemd and journald In-Reply-To: <20160522124140.GA3630@free.fr> References: <20160522124140.GA3630@free.fr> Message-ID: <20160523100709.3e2f0feb@itchy> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hi! Le Sun, 22 May 2016 14:41:40 +0200, "Yann E. MORIN" 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