Bug#853940: systemd: RestrictAddressFamilies causes services to fail to start on powerpc

Phil Armstrong phil at kantaka.co.uk
Thu Feb 2 14:19:43 GMT 2017


On Feb 2 2017, Michael Biebl wrote:

>Am 02.02.2017 um 11:46 schrieb Phil Armstrong:
>> Package: systemd
>> Version: 232-15
>> Severity: normal
>>
>> A recent update to systemd enabled SECCOMP, after which any service using
>> RestrictAddressFamilies, MemoryDenyWriteExecute or RestrictRealtime fails
>> to start. This includes udev, systemd-logind, systemd-journld etc etc.
>>
>
>[..]
>
>>
>> -- System Information:
>> Debian Release: 8.7
>>   APT prefers stable
>>   APT policy: (650, 'stable'), (600, 'unstable')
>> Architecture: powerpc (ppc)
>
>you reported this for powerpc. seccomp support has been enabled on that
>architecture for almost a year. The recent update, which I assume you
>are referring to, was for enabling it on ppc64 (232-12).
>
>Or did you mean something else?

Were these entries added to the systemd service files only recently? These 
services all started breaking for me about a week or two ago. They were 
fine beforehand.

The machine in question vaguely tracks sid. It did track testing until 
powerpc was dropped from the next Debian release & testing went away.

Phil




More information about the Pkg-systemd-maintainers mailing list