New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Socket::SOMAXCONN() on Linux #8983
Comments
From @schweikertCreated by @schweikertThis is a bug report for perl from david@schweikert.ch, ----------------------------------------------------------------- Cheers, PS: see also bug #44259 about a similar problem on Solaris. Perl Info
|
From jns@gellyfish.comHi,
I'm not so sure that this is really a "bug" - the Socket module is #define SOMAXCONN 128 Now it might be possible for Socket to gather the runtime value of this My suggestion would be, in the first instance, to create a non-core CPAN The advantage (as I see it) of having this initially non-core is that it Of course it might be worth updating the documentation for Socket to /J\ |
The RT System itself - Status changed from 'new' to 'open' |
From ams@toroid.orgAt 2007-08-02 21:31:08 +0100, jns@gellyfish.com wrote:
I agree. Probing (this, and other) runtime parameters should be left to
Good idea. -- ams |
From @schweikertOn Thu, Aug 02, 2007 at 20:28:18 -0700, Abhijit Menon-Sen via RT wrote:
Nobody is going to require a CPAN module only to query the value of Cheers |
From jns@gellyfish.comOn Fri, 2007-08-03 at 08:34 +0200, David Schweikert wrote:
Well to be fair they are already using a module to get the value of The great advantage of having the determination of the runtime This doesn't preclude such a module going into the core or even that It appears from looking at the documentation for Linux and FreeBSD that It would be nice if there were a single sysctl interface that could be SoOoo, if everyone's basically happy with changing the documentation as Does that sound like a plan? /J\ |
From jns@gellyfish.comHi,
We'd need to know which OS had which behaviour and possibly introduce a I'd also rather not have making any changes to the behaviour of listen()
I have a suspicion that anyone who cares about this will already know
I just see it as a way of moving this forward and not making it a We still need to get some understanding of the behaviour on other OS /J\ |
From @schweikertHi Jonathan, On Fri, Aug 03, 2007 at 14:03:55 +0100, Jonathan Stowe wrote:
What about the following: document that if you want the highest possible I don't think that many applications really care about what the
I am still not convinced that anybody would start using such a module. Thanks a lot for your rapid response and help! Cheers |
Migrated from rt.perl.org#44329 (status was 'open')
Searchable as RT44329$
The text was updated successfully, but these errors were encountered: