2011/10/5 Michael Bushkov <bush...@freebsd.org>: > There are probably 2 things here: > 1. There's some error in nsswitch<->nscd communication protocol that > causes nsswitch to write into the closed socket. This is not trivial > to investigate and will require analyzing nscd and client process logs > side by side (and possibly adding some more logging). > 2. Consequences of the aforementioned problem can probably be > corrected by using _setsockopt(..., SO_NOSIGPIPE) in > __open_cached_connection() in nscachedcli.c > (http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libc/net/nscachedcli.c?rev=1.3). > > I have no access to FreeBSD desktop at the moment - Artem, it would be > cool if you can try the second solution.
That's exactly what I did and it fixed the problem on the client side. I've posted the patch setting SO_NOSIGPIPE earlier in this thread: http://lists.freebsd.org/pipermail/freebsd-hackers/2011-October/036539.html --Artem _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
