> POSIX also specifies the errors EDESTADDRREQ, EACCES, another EINVAL for
> shut down sockets, and ENOBUFS. The last 3 "may" cause listen() to fail
> and the others (including the first EINVAL) "shall" cause it to fail.
EDESTADDRREQ seems to not be generated, inste
using a
> call other than listen()?
>
> That it causes a panic when the SYN cache is enabled isn't really
> a technical reason, it's a circumstantial reason.
The manpage change does not reflect the change in the patch :)
It should be:
[EINVAL]The sock
yncache however, a panic can be triggered
by normal ACK packets.
In your example, the listen is buried in the bowels of the RPC code.
The solution should be to reject the listen() with EINVAL (which seems
to be that standard-mandated error for connected sockets); patch
attached.
Any thought
On Mon, 2001/05/21 at 14:43:09 +0100, Ian Dowse wrote:
> In message <[EMAIL PROTECTED]>, Barney Wolff writes:
> >1. Multi-homed hosts are in fact very common, especially in
> >corporate environments. To get the right source addr in
> >its reply, the server must open separate sockets on e
Hello,
I would like to commit a really small patch that makes getsockname
fill the sockaddr for non-bound PF_LOCAL sockets with sun_noname,
instead of just setting the length parameter to 0 and return (without
an error) like it does now.
PF_INET and PF_INET6 sockets, for example, behave like this
On Wed, Mar 28, 2001 at 08:31:01AM +1000, Daniel Wong wrote:
> I can't get my sysctl to come up in my sysctl -A
>
> I have in my kernel code defined SYSCTL_STRUCT(_net_inet_ip, ... ...) and
> under in.h (I'm working under Ip) added my sysctl definition, i presume it's
> just adding the extra enum
