Comment # 61 on bug 1165351 from Thomas Blume

(In reply to Luis Chamberlain from comment #60)
> (In reply to Franck Bui from comment #59)
> > (In reply to Thomas Blume from comment #57)
> > > Franck, if you have no objections, I would send this patch upstream.
> > 
> > Sure, go ahead.
> 
> So I still am a bit perplexed about one thing. Why is this issue only being
> observed now? I checked the code lineage at least in systemd, and this seems
> to have existed for a long time now.

IMHO, using the rlimits for the systemd user daemon in libtirpc has never
worked, but that was hidden because the NOFILES for pid1 were also lower.
The issue became visible after increasing the NOFILES for pid1.
When having the rlimits for the systemd user dameon applied at he time of the
libtirpc call, it starts working. This is what my patch does.
However, it seems that upstream still doubts that this is a systemd issue, see:

https://github.com/systemd/systemd/pull/15423

There is no question that the code in libtirpc also needs to be improved, but
the trigger of this bug, at least in a standard tumbleweed installation, is
that libirpc is using an rlimit that isn't applied yet.