delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
Date: | Tue, 22 Feb 2005 15:45:17 -0500 |
From: | Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: children of init ignore STOP and CONT signals |
Message-ID: | <20050222204516.GA453@trixie.casa.cgf.cx> |
Reply-To: | cygwin AT cygwin DOT com |
References: | <BAY1-F321629E2FEB020E1F60A3BDB620 AT phx DOT gbl> |
Mime-Version: | 1.0 |
In-Reply-To: | <BAY1-F321629E2FEB020E1F60A3BDB620@phx.gbl> |
User-Agent: | Mutt/1.4.1i |
On Tue, Feb 22, 2005 at 06:13:29PM +0000, Sam Inala wrote: >The stop and continue signals seem to be ignored by cygwin processes if >they are children of init (process id 1). The signals are handled >correctly if the targets are children of a bash process. Correct. This is longstanding behavior. Stop signals are ignored if there is no parent process. Apparently, the theory is that since SIGSTOP is a UNIX thing, it makes no sense to stop a process if no other process is around to recognize that fact. This prevents a user from typing CTRL-Z and creating a suspended process which requires restarting from another window. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |