From owner-freebsd-current Mon Jun 8 18:40:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24601 for freebsd-current-outgoing; Mon, 8 Jun 1998 18:40:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24487 for ; Mon, 8 Jun 1998 18:40:05 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id SAA22990; Mon, 8 Jun 1998 18:40:05 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp01.primenet.com, id smtpd022960; Mon Jun 8 18:40:03 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id SAA25156; Mon, 8 Jun 1998 18:40:00 -0700 (MST) From: Terry Lambert Message-Id: <199806090140.SAA25156@usr07.primenet.com> Subject: Re: Threads library bug To: jb@cimlogic.com.au (John Birrell) Date: Tue, 9 Jun 1998 01:40:00 +0000 (GMT) Cc: tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <199806090058.KAA09481@cimlogic.com.au> from "John Birrell" at Jun 9, 98 10:58:34 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Check for a read or write with nbytes = 0. I'm about to commit > a fix for this. Thanks; I'll test it whenever you want... though I'm going to migrate it to 2.6 for the testing. > This is the problem referred to on HighWind's > download page (http://www.highwind.com/). My failure just gives a zero length .dbb (dbm btree) file; it doesn't spin forever or consume CPU. Those problems are most likely another problem... probably passing getdtablesize()'s return as the first argument of select(2), instead of FD_SETSIZE. The LDAP and ACAP code had similar (bogus) assumptions (that the FD_SETSIZE would be at least as large as the getdtablesize() and/or sysconf(_SC_OPEN_MAX) return values). If this is the case, then it's not a threads library problem, but a source problem. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message