Comment # 62 on bug 1165351 from Jaime Caama�o Ruiz

I took this off Thomas' hands.

I have not seen it specifically mentioned here, apologies if it was already
known, but this seem to be ultimately caused by the bump of nr_open introduced
in systemd 240 [1]. systemd inherits its nofile limit (hard & soft) from
nr_open after this bump. Before this change, we would be running a nr_open of
1024*1024=1048576 but from 240 it is bumped to 1073741816. A possible
workaround is to use the build option provided by systemd
Dbump-proc-sys-fs-nr-open, to avoid this bump and remain on the previous value,
until we have a permanent fix in libtirpc. Frank, what do you think of this?

In the meantime, steved has applied a patch to use the soft limit instead of
the hard limit, but this wont fix the issue for systemd PID1. I will let him
know.

[1]
https://github.com/systemd/systemd/blob/1742aae2aa8cd33897250d6fcfbe10928e43eb2f/NEWS#L96