View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0003349||unreal||ircd||public||2007-05-19 02:06||2019-05-16 19:00|
|Target Version||Fixed in Version||4.2.3|
|Summary||0003349: Config and MAXCONNECTIONS|
|Description||Have ./Config get the hard limit (ulimit -n) and refuse values greater than it.|
This can be done by outputting an error, or just using the hard limit if a greater value is specified.
|Tags||No tags attached.|
|3rd party modules|
fdcheck.patch (1,259 bytes)
||Patch attached, tested on a Gentoo and CentOS systems, worked fine.|
|Reservation: ulimit -is a inbuilt shell command-. It does not work on all shells.|
||Is there a way to have config check the same way Unreal checks?|
[quote]Reservation: ulimit -is a inbuilt shell command-. It does not work on all shells.[/quote]
Well, considering that Config runs through /bin/sh, and that, at least as far as I know, ulimit -n can be considered reasonably standard on most /bin/sh implementations, I see no reason we can't do that (and fall back to our 1024 default just in case).
Or, a simple minitool to grab the fd hardlimit would not be difficult to include (ie same method as unreal as Bugz suggested).
In 4.2.3 we have this new 'auto' mode, and at runtime we will use up to that value. We will use lower if less fd's are available on the shell. Should make it a lot more easy for users.
|2007-05-19 02:06||Stealth||New Issue|
|2007-05-19 03:55||nate||File Added: fdcheck.patch|
|2007-05-19 03:55||nate||Note Added: 0014176|
||Note Added: 0014178|
||Status||new => feedback|
|2007-05-19 12:44||Stealth||Note Added: 0014179|
|2007-05-19 14:49||aquanight||Note Added: 0014181|
|2019-05-16 19:00||syzop||Assigned To||=> syzop|
|2019-05-16 19:00||syzop||Status||feedback => closed|
|2019-05-16 19:00||syzop||Resolution||open => fixed|
|2019-05-16 19:00||syzop||Note Added: 0020673|
|2019-05-16 19:00||syzop||Status||closed => resolved|
|2019-05-16 19:00||syzop||Target Version||=> 4.2.4|
|2019-05-16 19:00||syzop||Fixed in Version||=> 4.2.3|
|2019-05-16 19:00||syzop||Target Version||4.2.4 =>|