Message-ID: <49B605A0.70304@columbus.rr.com>
Date: Tue, 10 Mar 2009 02:16:00 -0400
From: Paul McFerrin <pmcferrin@columbus.rr.com>
Reply-To: pmcferrin@columbus.rr.com
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: minTTY will not interrupt 'locked' process
References: <49B58491.5080101@columbus.rr.com> <416096c60903091432w1c4b2d2fjc1cf23896fd8ef9d@mail.gmail.com> <20090310024849.GA17042@ednor.casa.cgf.cx>
In-Reply-To: <20090310024849.GA17042@ednor.casa.cgf.cx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

I'll watch for it to occur again.  Is there anything I can collect for 
you in this besides a ps(1) showing the process is inactive or should I 
just forget it for now.

Christopher Faylor wrote:
> On Mon, Mar 09, 2009 at 09:32:36PM +0000, Andy Koppe wrote:
>   
>>> Several times recently, I have executed a command on a "file" that was
>>> apparently "locked". ?Any attempts to perform any reads/opens on the file
>>> would block. ?When it happens, the only was out is to terminate minTTY
>>> session (no ctl-C or ctl-\ will terminate). ?Is this a normal situation?
>>>       
>> I'm afraid I don't know about those locked files, but in any case this
>> sounds more like a general Cygwin question. When you press Ctrl-C or
>> Ctrl-\, MinTTY simply writes the corresponding control character to
>> the pty device connecting it to its child process. The terminal driver
>> normally turns that into a SIGINT or SIGQUIT, but applications can
>> override that, or choose to ignore signals. Also, Cygwin can't deliver
>> signals while a program is executing a Win32 function.
>>     
>
> Right.  If a process is blocked in a situation where Cygwin isn't
> expecting it, like when reading a disk file, then signals won't have
> much effect.  This is actually more than a little like what happens
> Linux when you try to access a file on, say, a bad disk.  Signals don't
> allow you to stop the process there either.
>
> 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/
>
>
>   

--
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/