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

[Michael Biebl]

Am 01.08.2016 um 23:40 schrieb Felipe Sateler:
> So I think the kernel should enable SECCOMP.

I agree, unless SECCOMP on arm has some unwanted side-effects.
Felipe, can you file a bug report against the linux package accordingly?

> However, I think systemd should also simply (warn and) ignore seccomp
> calls if seccomp is not available in the current kernel.

I agree as well, Systemd should log an error and continue.
We need to file a bug report upstream for that? Any takers?

Assuming upstream actually decides to make SECCOMP (once enabled) a hard
dependency, we need to find a different solution, like a check in the
maintainer scripts. That said, we should first try to get that adressed
upstream.

Regards,
Michael

-- 
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/20160803/db474fd5/attachment-0002.sig>