[systemd-devel] SystemCallFilter=~@resources broken in F26/systemd233

Reindl Harald h.reindl at thelounge.net
Sat Sep 30 12:47:29 UTC 2017



Am 30.09.2017 um 14:38 schrieb Lennart Poettering:
> On Sa, 23.09.17 15:38, Reindl Harald (h.reindl at thelounge.net) wrote:
> 
>> with Fedroa 25 that was no problem, on F26 httpd, mysqld and so on are
>> breaking
>>
>> [root at testserver:~]$ rpm -q systemd
>> systemd-233-6.fc26.x86_64
>>
>> [root at testserver:~]$ rpm -q glibc
>> glibc-2.25-10.fc26.x86_64
>>
>> @resources    System calls for changing resource limits, memory and
>> scheduling parameters (setrlimit(2), setpriority(2)
>>
>> Process 7320 (php71) of user 0 dumped core.#012#012Stack trace of thread
>> 7320:#012#0  0x00007fe043c14f29 __getrlimit (libc.so.6)#012#1
>> 0x00007fe043c0e771 __get_child_max (libc.so.6)#012#2  0x00007fe043be5434
>> __sysconf (libc.so.6)#012#3  0x0000562a0c61062e getmaxchild (bash)#012#4
>> 0x0000562a0c5c482c initialize_job_control (bash)#012#5 0x0000562a0c597929
>> shell_initialize (bash)#012#6  0x0000562a0c59b03d main (bash)#012#7
>> 0x00007fe043b2f50a __libc_start_main (libc.so.6)#012#8  0x0000562a0c59be5a
>> _start (bash)
> 
> I am pretty confident that this will fix the issue for you:
> https://github.com/systemd/systemd/pull/6952

only if systemd in Fedora would be proper maintained after release but 
then https://bugzilla.redhat.com/show_bug.cgi?id=1399991 would have been 
fixed for F25 in it's life-cycle when patches are available all the time


More information about the systemd-devel mailing list