From: Andreas Schwab <schwab@suse.de>
To: linux-os@analogic.com
Cc: Daniel Jacobowitz <dan@debian.org>,
Olivier Croquette <ocroquette@free.fr>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Scheduler: SIGSTOP on multi threaded processes
Date: Thu, 05 May 2005 15:30:09 +0200 [thread overview]
Message-ID: <jezmv9ream.fsf@sykes.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0505050814340.24130@chaos.analogic.com> (Richard B. Johnson's message of "Thu, 5 May 2005 08:24:54 -0400 (EDT)")
"Richard B. Johnson" <linux-os@analogic.com> 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."
next prev parent reply other threads:[~2005-05-05 13:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 17:37 Scheduler: SIGSTOP on multi threaded processes Olivier Croquette
2005-05-04 18:16 ` Richard B. Johnson
2005-05-04 19:16 ` Daniel Jacobowitz
2005-05-04 21:06 ` Alex Riesen
2005-05-05 0:42 ` Richard B. Johnson
2005-05-05 0:33 ` Richard B. Johnson
2005-05-05 0:45 ` Richard B. Johnson
2005-05-05 12:24 ` Richard B. Johnson
2005-05-05 13:14 ` Denis Vlasenko
2005-05-05 13:30 ` Andreas Schwab [this message]
2005-05-05 22:04 ` Miquel van Smoorenburg
2005-05-06 23:15 ` Problem while stopping many threads within a module Yuly Finkelberg
2006-04-20 8:43 ` shikha
2005-05-10 20:59 ` Scheduler: SIGSTOP on multi threaded processes Olivier Croquette
2005-05-10 21:12 ` Roland McGrath
2005-05-11 18:58 ` Olivier Croquette
2005-05-10 23:05 ` Alex Riesen
2005-05-05 1:04 ` Andy Isaacson
2005-05-04 19:10 ` Alexander Nyberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jezmv9ream.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=dan@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=ocroquette@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.