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 Solaris #8980
Comments
From @schweikertCreated by @schweikertThis is a bug report for perl from david@schweikert.ch, ----------------------------------------------------------------- $ ndd /dev/tcp tcp_conn_req_max_q The consequence of the fact that Socket::SOMAXCONN() always returns 5 on I propose to do one of the following: - Find out the real value at run-time when Socket::SOMAXCONN() is called. I - Return a higher fixed value on Solaris. I think that a minimum like 128 should Thanks and Cheers Perl Info
|
From @nwc10On Mon, Jul 30, 2007 at 06:09:12AM -0700, David Schweikert wrote:
How does Solaris document that a C program should query this value? Nicholas Clark |
The RT System itself - Status changed from 'new' to 'open' |
From @smpetersOn Mon, Jul 30, 2007 at 07:00:57PM +0100, Nicholas Clark wrote:
This is very old, but seems very relevant... http://www.usenix.org/publications/perl/perl15.html On almost every socket implementation in existence, the maximum queue length Steve Peters |
From @schweikertOn Mon, Jul 30, 2007 at 11:23:26 -0700, Nicholas Clark via RT wrote:
It is not documented and I don't think that it can be done without However, in the "Solaris Tunable Parameters Reference Manual" it is I was courious to see if the "tcp_conn_req_max_q" was also relevant to I have also seen in the source code that the backlog parameter is Cheers |
From @doughera88On Mon, 30 Jul 2007, Nicholas Clark wrote:
They don't, as far as I've been able to tell.
Apparently. The query simply returns a single number, so very $ /usr/sbin/ndd /dev/tcp tcp_conn_req_max_q The NOTES section from the Solaris 8 man pages has the following caveats: The parameters supported by each driver may change from The ioctl() command that ndd uses to communicate with The meanings of many ndd parameters make sense only if you but this one, at least, appears to have been stable since somewhere -- |
From @schweikertOn Tue, Jul 31, 2007 at 06:25:49 -0700, Andy Dougherty via RT wrote:
Note however that this value is only pertinent for TCP sockets and not Cheers |
From @schweikertOn Mon, Jul 30, 2007 at 11:23:26 -0700, Nicholas Clark via RT wrote:
It is not documented and I don't think that it can be done without However, in the "Solaris Tunable Parameters Reference Manual" it is I was courious to see if the "tcp_conn_req_max_q" was also relevant to I have also seen in the source code that the backlog parameter is Cheers |
From @schweikertOn Tue, Jul 31, 2007 at 06:25:49 -0700, Andy Dougherty via RT wrote:
Note however that this value is only pertinent for TCP sockets and not Cheers |
Migrated from rt.perl.org#44259 (status was 'open')
Searchable as RT44259$
The text was updated successfully, but these errors were encountered: