Date: Tue, 04 Oct 2011 19:54:05 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Artem Belevich <art@freebsd.org> Cc: hackers@freebsd.org, Trond =?utf-8?Q?Endrest=C3=B8l?= <Trond.Endrestol@fagskolen.gjovik.no> Subject: Re: Does anyone use nscd? Message-ID: <86fwj84p8i.fsf@ds4.des.no> In-Reply-To: <CAFqOu6iw12BbvmS9NH3fNzWqQR1YvYrqyM6JFrYDfs2=HQ3w_w@mail.gmail.com> (Artem Belevich's message of "Tue, 4 Oct 2011 10:16:32 -0700") References: <86sjn84wco.fsf@ds4.des.no> <alpine.BSF.2.00.1110041800290.18373@mail.fig.ol.no> <86obxw4s4w.fsf@ds4.des.no> <CAFqOu6iw12BbvmS9NH3fNzWqQR1YvYrqyM6JFrYDfs2=HQ3w_w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Artem Belevich <art@freebsd.org> writes: > And I do have a way to reproduce the SIGPIPE problem. Populate ~30K > entries in NIS passwd database, enable nscd and then run top. In my > case top used to die with SIGPIPE pretty reliably. I've fixed the > issue locally by setting SO_NOSIGPIPE on the socket in > __open_cached_connection() in lib/libc/net/nscachedcli.c and I've been > running with the fix for few months now. Any chance of getting a backtrace from an unpatched nscd? Ideally with the change described here: http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dbin/136073#reply1 To test, stop nscd, then run it from the command line like so: $ su - # cd /tmp # ulimit -c 0 # /usr/sbin/nscd -nst (do something in another terminal that causes it to crash) # echo backtrace | gdb -batch -x /dev/stdin /usr/sbin/nscd nscd.core and send me the output from both nscd and gdb once it crashes.=20=20 DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86fwj84p8i.fsf>