From: Jack Mitchell <ml@communistcode.co.uk>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: systemd post-install failure
Date: Mon, 22 Apr 2013 15:13:21 +0100 [thread overview]
Message-ID: <51754581.3090005@communistcode.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 650 bytes --]
Booting master today I had a systemd fault. Enabling debugging I
captured the (attached) output. The gist of which is:
.....
Spawned /lib/systemd/system-generators/systemd-system-update-generator as 81
.....
Received SIGCHLD from PID 81 (n/a).
Got SIGCHLD for process 90 (systemd-sysctl)
Child 90 died (code=exi
So, looking into systemd-system-update-generator, it seems this is what
takes card of the post install scripts, which I know we're having
problems with.
Is there anything I can do to help?
Cheers,
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
[-- Attachment #2: screenlog.0 --]
[-- Type: application/octet-stream, Size: 26311 bytes --]
next reply other threads:[~2013-04-22 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 14:13 Jack Mitchell [this message]
2013-04-22 14:40 ` systemd post-install failure Burton, Ross
2013-04-22 14:44 ` Jack Mitchell
2013-04-22 14:56 ` Burton, Ross
2013-04-22 15:03 ` Jack Mitchell
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=51754581.3090005@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=openembedded-core@lists.openembedded.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox