> I've started to use Linux 2.1.103 on my i486 running a glibc 2.1
> snapshot. Looking at my log files I noticed a number of the following
> entries:
>
> May 25 20:39:41 arthur innd: localhost:17 cant setsockopt(SNDBUF) Invalid argument
> May 25 20:39:41 arthur innd: localhost:17 cant setsockopt(RCVBUF) Invalid argument
>
> Ping shows a similar behaviour:
>
> $ ping localhost
> setsockopt: SO_RCVBUF: Invalid argument
>
> strace give the following output:
> socket(PF_INET, SOCK_RAW, IPPROTO_ICMP) = 3
> setsockopt(3, SOL_SOCKET, SO_RCVBUF, [49152], 4) = -1 EINVAL (Invalid argument)
^^^^^^^
The default SK_RMEM_MAX is 32768 bytes. If you want more change the
/proc/sys/net/core/{rmem,wmem}_max sysctls (note that they always contain twice
the real value). The difference between 2.0 and 2.1 is that 2.1 complains
about a bogus value (with EINVAL), while 2.0 silently fixed it.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu