Date: Wed, 6 Jan 1999 15:17:32 -0600 From: "Richard Seaman, Jr." <dick@tar.com> To: current@FreeBSD.ORG Subject: Re: Squid + linuxthreads in action Message-ID: <19990106151732.A752@tar.com> In-Reply-To: <E0zy08Z-0007Wm-00@fanf.noc.demon.net>; from Tony Finch on Wed, Jan 06, 1999 at 09:05:07PM %2B0000 References: <E0zxzBQ-0007Tt-00@fanf.noc.demon.net> <E0zxzBQ-0007Tt-00@fanf.noc.demon.net> <19990106142240.A375@tar.com> <E0zy08Z-0007Wm-00@fanf.noc.demon.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 06, 1999 at 09:05:07PM +0000, Tony Finch wrote: > "Richard Seaman, Jr." <dick@tar.com> wrote: > >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. > > > >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? > > That's right. (The aio_* routines use threads? I thought they were > just syscalls.) In a sense they are just syscalls. But I think they use "kernel threads" inside the kernel. I'm not sure the threads are accessible in user space. > >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. > > That's what it looks like. Ok. I'll try to work on it. -- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990106151732.A752>