Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262105AbVEENa0 (ORCPT ); Thu, 5 May 2005 09:30:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262109AbVEENaZ (ORCPT ); Thu, 5 May 2005 09:30:25 -0400 Received: from cantor.suse.de ([195.135.220.2]:2492 "EHLO mx1.suse.de") by vger.kernel.org with ESMTP id S262108AbVEENaM (ORCPT ); Thu, 5 May 2005 09:30:12 -0400 From: Andreas Schwab To: linux-os@analogic.com Cc: Daniel Jacobowitz , Olivier Croquette , LKML Subject: Re: Scheduler: SIGSTOP on multi threaded processes References: <4279084C.9030908@free.fr> <20050504191604.GA29730@nevyn.them.org> X-Yow: UH-OH!! We're out of AUTOMOBILE PARTS and RUBBER GOODS! Date: Thu, 05 May 2005 15:30:09 +0200 In-Reply-To: (Richard B. Johnson's message of "Thu, 5 May 2005 08:24:54 -0400 (EDT)") Message-ID: User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/22.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 863 Lines: 24 "Richard B. Johnson" writes: > I don't think the kernel handler gets a chance to do anything > because SYS-V init installs its own handler(s). It's impossible to install a handler for SIGSTOP. > There are comments about Linux misbehavior in the code. It turns out > that I was right about SIGSTOP and SIGCONT... No, you are wrong. SIGTSTP != SIGSTOP. Andreas. -- Andreas Schwab, SuSE Labs, schwab@suse.de SuSE Linux Products GmbH, Maxfeldstra?e 5, 90409 N?rnberg, Germany Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/