setsockopt(RCVBUF) Invalid argument with 2.1.103

Andreas Jaeger (aj@arthur.rhein-neckar.de)
Tue, 26 May 1998 20:02:40 +0200 (CEST)

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)
write(2, "setsockopt: SO_RCVBUF: Invalid a"..., 40setsockopt: SO_RCVBUF: Invalid argument) = 40

Any ideas what might be the problem? Isn't SO_RCVBUF/SO_SNDBUF
supported anymore?

Andreas

-- 
 Andreas Jaeger   aj@arthur.rhein-neckar.de    jaeger@informatik.uni-kl.de
  for pgp-key finger ajaeger@alma.student.uni-kl.de


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu