From owner-freebsd-current Wed Jan 6 12:23:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03354 for freebsd-current-outgoing; Wed, 6 Jan 1999 12:23:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03347 for ; Wed, 6 Jan 1999 12:23:19 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.1/8.9.1) id OAA01855; Wed, 6 Jan 1999 14:22:40 -0600 (CST) (envelope-from dick) Date: Wed, 6 Jan 1999 14:22:40 -0600 From: "Richard Seaman, Jr." To: Tony Finch Cc: current@FreeBSD.ORG Subject: Re: Squid + linuxthreads in action Message-ID: <19990106142240.A375@tar.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Tony Finch on Wed, Jan 06, 1999 at 08:04:00PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 06, 1999 at 08:04:00PM +0000, Tony Finch wrote: > When the parent Squid process shuts down it leaves behind a pile of > orphan processes (the async-io handler threads). A glance at the aio > code reveals that Squid expects the pthread library to kill them -- > they just loop indefinitely. They also keep the listen socket open, so > the RunCache script can't restart Squid :-( A clarification question -- the async-io threads you're referring to are threads created with pthread_create from the linux threads library, and not threads created by the FreeBSD aio routines, correct? If so, this would indicate a bug in the linux threads port and/or the shared signal handling code -- all threads are supposed to be killed when the "main thread" exits. -- Richard Seamman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message