Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

[Michael Biebl]

Am 28.07.2016 um 22:01 schrieb Rick Thomas:
> No.  This is a stock kernel.  It’s available from both testing and unstable repos.  The machine itself is a SheevaPlug.  Nothing custom about it.
> 
> What makes you think it’s custom?

This was more of a question then a statement.
I wanted to rule out, that the kernel was missing any relevant features.

I assume the previous version worked properly and the addition of

SystemCallFilter=~@clock @cpu-emulation @debug @keyring @module @mount
@obsolete @raw-io

is causing the problem? If you comment out that line from
systemd-journald.service, does it start properly?

SystemCallFilter uses libseccomp, maybe libseccomp on armel is not fully
functional and we need to reassign this.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20160728/1ac8c692/attachment-0002.sig>