X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <49B58491.5080101@columbus.rr.com> References: <49B58491 DOT 5080101 AT columbus DOT rr DOT com> Date: Mon, 9 Mar 2009 21:32:36 +0000 Message-ID: <416096c60903091432w1c4b2d2fjc1cf23896fd8ef9d@mail.gmail.com> Subject: Re: minTTY will not interrupt 'locked' process From: Andy Koppe To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 > Several times recently, I have executed a command on a "file" that was > apparently "locked". =A0Any attempts to perform any reads/opens on the fi= le > would block. =A0When it happens, the only was out is to terminate minTTY > session (no ctl-C or ctl-\ will terminate). =A0Is 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. Andy -- 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/