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

[Michael Biebl]

Am 29.07.2016 um 23:29 schrieb Rick Thomas:
> Hmmm…  Curiouser and curiouser!
> 
> I upgraded a VM (amd64) to latest Sid (with systemd version 231-1).  The problem is *not* present there.
> 
> The problem may be specific to arm hardware?  I’ll try it on a PowerPC G4 (Apple Mac PPC) machine later today.

I think this might be arch specific, yes.
See my reply earlier:

> 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/20160730/63bc9a14/attachment-0002.sig>