From owner-freebsd-current Mon Jun 8 11:42:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14913 for freebsd-current-outgoing; Mon, 8 Jun 1998 11:42:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (daemon@smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14765 for ; Mon, 8 Jun 1998 11:41:36 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id LAA00682 for ; Mon, 8 Jun 1998 11:41:15 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp04.primenet.com, id smtpd000659; Mon Jun 8 11:41:09 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id LAA13449 for current@freebsd.org; Mon, 8 Jun 1998 11:41:08 -0700 (MST) From: Terry Lambert Message-Id: <199806081841.LAA13449@usr04.primenet.com> Subject: Threads library bug To: current@FreeBSD.ORG Date: Mon, 8 Jun 1998 18:41:08 +0000 (GMT) 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 I have tracked down an LDAP bug to the threads library. Specifically, if the "ldif2ldbm" program is linked against libc_r (which it does not require unless the ldap server itself is built threaded), then it produces zero-length .dbb database files. If it is linked against libc, the problem goes away. This appears to be a problem with the dbm routines using the libc_r system calls to do their thing? I am attempting to identify the precise problem, but you should not expect a fix for a while. 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