I wrote a test program and verified that the call to bind() with a bogus
address family succeeds, instead of setting errno to EINVAL as documented.
This occurs in 2.2 kernels, and appears identical in 2.0.36.
Is there some reason to avoid doing this check? Or is this just a bug?
Or should the IP(4) man page get fixed?
Thanks,
Mark Gritter
mark@erdos.stanford.edu
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.rutgers.edu