From owner-freebsd-stable Fri Apr 27 18:18:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from btw.plaintalk.bellevue.wa.us (btw.plaintalk.bellevue.wa.us [206.129.5.130]) by hub.freebsd.org (Postfix) with ESMTP id 644DF37B423; Fri, 27 Apr 2001 18:18:44 -0700 (PDT) (envelope-from dennisg@software-munitions.com) Received: from localhost (dennisg@localhost) by btw.plaintalk.bellevue.wa.us (8.11.3/8.11.3) with ESMTP id f3S1IXJ05698; Fri, 27 Apr 2001 18:18:33 -0700 (PDT) (envelope-from dennisg@software-munitions.com) Date: Fri, 27 Apr 2001 18:18:33 -0700 (PDT) From: Dennis Glatting X-X-Sender: To: , Subject: problems with the resolver under 4.3 Message-ID: <20010427181312.Q682-100000@btw.plaintalk.bellevue.wa.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have tracked down some problems with slurpd on a multi processor machine and have discovered slurpd consistently hangs in res_send() -- I have multiple slaves. I don't know exactly what is going on in res_send(), since I am presently unable to step through it, however I see there are many static variables defined in the file (lib/libc/net/res_send.c) and the code is ancient compared to the BIND source under contrib. Are there known threading issues on a multi processor machine with res_send()? Are there plans to update the resolver library? -- Dennis Glatting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message