From owner-freebsd-questions@FreeBSD.ORG Sat Oct 30 21:51:32 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E23616A4CF for ; Sat, 30 Oct 2004 21:51:32 +0000 (GMT) Received: from ms-smtp-01-eri0.southeast.rr.com (ms-smtp-01-lbl.southeast.rr.com [24.25.9.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7DAB43D62 for ; Sat, 30 Oct 2004 21:51:31 +0000 (GMT) (envelope-from jason@ec.rr.com) Received: from [192.168.1.103] (cpe-065-184-172-100.ec.rr.com [65.184.172.100])i9ULpSKj011572; Sat, 30 Oct 2004 17:51:29 -0400 (EDT) Message-ID: <41840D14.5000006@ec.rr.com> Date: Sat, 30 Oct 2004 17:52:20 -0400 From: jason User-Agent: Mozilla Thunderbird 0.8 (X11/20041025) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Drew Tomlinson References: <4183F8AE.6060006@mykitchentable.net> In-Reply-To: <4183F8AE.6060006@mykitchentable.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine cc: FreeBSD Questions Subject: Re: Pthreads Bug & Bacula X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Oct 2004 21:51:32 -0000 Drew Tomlinson wrote: > Can anyone tell me if or when the pthreads bug was fixed in version > 4? Google searches show some indication it was fixed in 4.9 and other > information that it was fixed in 4.10. I'm running 4.9-RELEASE-p4. > > Currently I'm following the instructions in pthreads-fix.txt but with > my DLT30 drive, I can see this will take many hours. I would really > appreciate it if someone can save me the time. :) I will upgrade to > 4.10 if I need to but would rather not if I don't have to. I don't > want to fix what isn't broken! :) > > Thanks, > > Drew > I was just updating my system yesterday and ran into the pthread bug. I had updated libxml2 and it was compiled with pthreads. To fix it I removed /var/db/ports/libxml2/options. When I recompiled it asked for a config, and I told it no pthreads. Now it works fine. So to answer your question the "bug" was never fixed because it is a design implementation issue. FreeBSD just exposes it right away instead of far off randomly in the future when you have long uptime(had to do with pids being recycled) so the general rule was disable them. Hope this helps.