This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: children of init ignore STOP and CONT signals


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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]