[pbs-devel] [PATCH proxmox-backup v3] etc: raise nofile soft limit to hard limit for proxmox-backup-proxy

[Christian Ebner]

On 11/20/25 4:05 PM, Thomas Lamprecht wrote:
> Am 20.11.25 um 15:32 schrieb Christian Ebner:
>> This is acceptable since PBS does not directly depend on problematic
>> select() calls as verified via `nm` and does not use it in linked
>> libraries to the best of my knowledge.
>>
> 
> Isn't above and

With above I intended to state that the PBS code itself does not call 
into select(), while below are dependencies on shared objects which 
might call into select() according to their symbols.

> 
>> Occurrences of the symbol according to `nm -D <shared-object>` are:
>>
>> /lib/x86_64-linux-gnu/libapt-pkg.so.7.0
>>                   U select at GLIBC_2.2.5
>> /lib/x86_64-linux-gnu/libpam.so.0
>>                   U select at GLIBC_2.2.5
>> /lib/x86_64-linux-gnu/libc.so.6
>> 000000000010e140 W select@@GLIBC_2.2.5
>> /lib/x86_64-linux-gnu/libcrypto.so.3
>>                   U select at GLIBC_2.2.5
> 
> above a contradiction? Or do I just misinterpret this?
> As it would seem to me that the usage of select symbols would in fact
> show that this might not be safe, or?
> 
> If the API calls into any function of those libs, that might might then create
> a FD >= 1024 inside which then could get passed down to any of their select
> calls?