From owner-freebsd-bugs Mon Jan 29 09:38:27 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA16507 for bugs-outgoing; Mon, 29 Jan 1996 09:38:27 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA16472 Mon, 29 Jan 1996 09:38:12 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA03732; Mon, 29 Jan 1996 10:35:56 -0700 From: Terry Lambert Message-Id: <199601291735.KAA03732@phaeton.artisoft.com> Subject: Re: problems running Executor/Linux on FreeBSD? To: d_burr@ix.netcom.com (Donald Burr) Date: Mon, 29 Jan 1996 10:35:56 -0700 (MST) Cc: freebsd-bugs@freebsd.org, freebsd-questions@freebsd.org, bugs@ardi.com, questions@ardi.com In-Reply-To: from "Donald Burr" at Jan 29, 96 03:55:50 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-bugs@freebsd.org Precedence: bulk > I'm running Executor/Linux 1.99q on my FreeBSD (2.1R) box, using > FreeBSD's Linux compatibility module. When I quit Executor, the > processes do not die (i.e. they still remain running or maybe zombied -- > I can't tell). For example: > > ncc-1701-d:24% ps aux | grep -i execu > d_burr 18876 95.2 0.1 0 0 v0 Z - 0:00.00 (executor) [ ... ] > > I'm not quite sure where to point the proverbial finger here. Is this a > FreeBSD bug, a Linux emulator bug, an Executor bug, or some bizarre > combination? Any ideas on if it's fixable, or how to fix it? or if it > will be fixed? I have an idea, but I don't know exactly what needs to be done. I suspect it's the alternate signal handling code sending a Linux style SIGCHLD to a BSD style parent process. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.