Hi Matevz,
OK, so you get
>>> Max processes unlimited unlimited processes ### <------ this
>>> [1509] root@cabinet-10-10-11 /var/log/xrootd# sudo -u xrootd bash -c "ulimit -a"
>>> max user processes (-u) 8192
While I get
Max processes 127401 127401 processes
ulimit -a
max user processes (-u) 1024
So, it's obvious you specified "-1" for the hard process limit (and maybe
more) but that doesn't cut it because Linux infinity doesn't work in
practice for many things (there is always a limit for all practical
purposes) and we'd like to know what that really is to not over-run the
system.
I suppose I can check for -1 but then I don't know what the practical
internal limit has to be set to except for some extremely large value.
>>> Any ideas what else to check / change?
Yes, while -1 is a valid specfication for most hard limits it's best not
to specify it. Use some good reasonble number or you're likely to run into
trouble.
This is the code that does this check:
>>>
>>> https://github.com/xrootd/xrootd/blob/master/src/Xrd/XrdConfig.cc#L855
Actually, all that code does is display the limit the the XrdScheduler
constructor used (actually set to). That's where the problem occurs.
Andy
########################################################################
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
|