Re: (Fwd) Re: 8.8.8: Useless error message about "getrequests"

Kari E. Hurtta (Kari.Hurtta@ozone.FMI.FI)
Mon, 2 Nov 1998 16:37:30 +0200 (EET)


Matti Aarnio:
> > Hello,
> >
> > it seems Linux 2.0.35 can return "no route to host" during an
> > accept() syscall, but not even syslog indicated which address was
> > involved. For debugging purposes it would be interesting to get that
> > information. I suspect someone behind a firewall is playing "routing
> > tricks".
>
> Once upon a time I wrote accept() code according to
> BSD man-pages, and did way too abortative error handling
> if the error-code return was unexpected.
>
> Then I installed that source to Solaris, and got LOTS of
> surprising error codes which (I think) did stem from the
> way how STREAMS works. That included things like "no route
> to host", ENOMEM, ENOSR...

Not surprising previous entry on KNOWNBUGS is:

| * accept() problem on SVR4.
|
| Apparently, the sendmail daemon loop (doing accept()s on the network)
| can get into a weird state on SVR4; it starts logging ``SYSERR:
| getrequests: accept: Protocol Error''. The workaround is to kill
| and restart the sendmail daemon. We don't have an SVR4 system at
| Berkeley that carries more than token mail load, so I can't validate
| this. It is likely to be a glitch in the sockets emulation, since
| "Protocol Error" is not possible error code with Berkeley TCP/IP.
|
| I've also had someone report the message ``sendmail: accept:
| SIOCGPGRP failed errno 22'' on an SVR4 system. This message is
| not in the sendmail source code, so I assume it is also a bug
| in the sockets emulation. (Errno 22 is EINVAL "Invalid Argument"
| on all the systems I have available, including Solaris 2.x.)
| Apparently, this problem is due to linking -lc before -lsocket;
| if you are having this problem, check your Makefile.

After all that was BSD Sendmail (now know as Open Source Sendmail).

Streams and linux are both non-BSD network stacks :-)

/ Kari Hurtta

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/