View Issue Details

IDProjectCategoryView StatusLast Update
0003349unrealircdpublic2019-05-16 19:00
ReporterStealth Assigned Tosyzop  
Status resolvedResolutionfixed 
OS*nixOS Version* 
Product Version3.3-alpha0 
Fixed in Version4.2.3 
Summary0003349: Config and MAXCONNECTIONS
DescriptionHave ./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.
TagsNo tags attached.
3rd party modules


2007-05-19 03:55


fdcheck.patch (1,259 bytes)


2007-05-19 03:55

reporter   ~0014176

Patch attached, tested on a Gentoo and CentOS systems, worked fine.


2007-05-19 08:35

reporter   ~0014178

Reservation: ulimit -is a inbuilt shell command-. It does not work on all shells.


2007-05-19 12:44

reporter   ~0014179

Is there a way to have config check the same way Unreal checks?


2007-05-19 14:49

reporter   ~0014181

[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).


2019-05-16 19:00

administrator   ~0020673

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.

Issue History

Date Modified Username Field Change
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
2007-05-19 08:35 stskeeps Note Added: 0014178
2007-05-19 08:35 stskeeps 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 =>