Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
This stems from #1962 where ALMA's exceedingly high numbers caused high memory consumption. However we actually already set decent limits at the spec file https://github.com/xrootd/xrootd/blob/7846b1cc8cb2b163d3ee6ddc07b983529d232f64/packaging/common/xrootd%40.service#L16 which would've actually limited the damage had we not explicitly overriden these at https://github.com/xrootd/xrootd/blob/7846b1cc8cb2b163d3ee6ddc07b983529d232f64/src/Xrd/XrdConfig.cc#L1190. So this is a discussion to start off whether such an artificial limiting is needed in code at all; where we override an admin written max/inifinity values to a code constant versus a more canonical systemd/per service configuration where admins choosing higher limits can choose them. We can of course warn users with extremely small fd limits as we'd encounter other issues then
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1