Re: Scheduler: SIGSTOP on multi threaded processes

On Thursday 05 May 2005 15:24, Richard B. Johnson wrote:
> 
> I don't think the kernel handler gets a chance to do anything
> because SYS-V init installs its own handler(s). There are comments
> about Linux misbehavior in the code. It turns out that I was
> right about SIGSTOP and SIGCONT...

No you are not.
--
vda

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Scheduler: SIGSTOP on multi threaded processes
    • From: Olivier Croquette <[email protected]>
  • Re: Scheduler: SIGSTOP on multi threaded processes
    • From: "Richard B. Johnson" <[email protected]>
  • Re: Scheduler: SIGSTOP on multi threaded processes
    • From: "Richard B. Johnson" <[email protected]>

• Prev by Date: Re: [RFC PATCH] Dynamic sched domains (v0.5)
• Next by Date: [patch] kbuild: display compile version
• Previous by thread: Re: Scheduler: SIGSTOP on multi threaded processes
• Next by thread: Re: Scheduler: SIGSTOP on multi threaded processes
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]