< said:
> Actually, the correct fix is most likely to redefine it to -1. :)
POSIX.1-200x draft 5 has this to say:
Implementations shall support values of backlog up to
SOMAXCONN, defined in
If listen( ) is called with a backlog argument value that is
less than
On Fri, 13 Apr 2001, Alfred Perlstein wrote:
> * Bruce Evans <[EMAIL PROTECTED]> [010412 22:25] wrote:
> > Changing the actual limit using either the sysctl or an option breaks
> > SOMAXCONN. I think the correct fix is to never define it change
> > whatever uses it to use sysconf(_SC_SOMAXCONN).
* Bruce Evans <[EMAIL PROTECTED]> [010412 22:25] wrote:
> On Thu, 12 Apr 2001, Jonathan Lemon wrote:
>
> > In article [EMAIL PROTECTED]>
>you write:
> > >Here are patches to make SOMAXCONN tunable from the config files.
> > >
> > >Right now, it's not possible to override SOMAXCONN.
> >
> >
On Thu, 12 Apr 2001, Jonathan Lemon wrote:
> In article [EMAIL PROTECTED]> you
>write:
> >Here are patches to make SOMAXCONN tunable from the config files.
> >
> >Right now, it's not possible to override SOMAXCONN.
>
> sysctl -w kern.ipc.somxconn=1024
>
> SOMAXCONN is just a compile time
In article [EMAIL PROTECTED]> you
write:
>Here are patches to make SOMAXCONN tunable from the config files.
>
>Right now, it's not possible to override SOMAXCONN.
sysctl -w kern.ipc.somxconn=1024
SOMAXCONN is just a compile time default, and yes it is not
currently tunable at config t
