Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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 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: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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/