Re: connect() hang under 2.1.11-ac3

Alan Cox (alan@lxorguk.ukuu.org.uk)
Wed, 18 Aug 1999 00:17:57 +0100 (BST)

> The clients freeze like this:
>
> [pid 1720] socket(PF_UNIX, SOCK_STREAM, 0) = 3
> [pid 1720] fcntl(3, F_SETFD, FD_CLOEXEC) = 0
> [pid 1720] connect(3, {sun_family=AF_UNIX, sun_path="/dev/log"}, 16 <unfinished ...>
>
> and syslogd is spinning thusly:

Eww syslogd really ought to use datagram mode. I didnt realise Linux still
didnt do this. Ok your syslogd has choked

> Syslog has a bunch of /dev/log sockets shown as CONNECTED by netstat during
> this time. I don't think it's that /syslogd has stopped listening on /dev/log,
> because when syslogd is stopped, the connect("/dev/log") fails immediately
> with ECONNREFUSED.

That is the behaviour I would expect if syslogd had choked and wasnt accepting
new connections. Why is of course the interesting question. libc should be
timing out connect to syslogd though if it uses connection oriented mode
which libc are you using ?

Alan

-
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/