-Original Message-
From: Benjamin Cao
Sent: Friday, November 13, 2015 3:46 PM
To: 'cygwin@cygwin.com'
Subject: CTRL-C not working in sh login mode?
Hi,
We invoke a shell using a *.bat file doing sh --login.
We have discovered that when wanting to kill a long running process
Hi,
We invoke a shell using a *.bat file doing sh --login.
We have discovered that when wanting to kill a long running process with
CTRL-C, it does not work.
Is this expected behavior?
I've found that to be the same even if I am doing bash --login -i in my *.bat
file.
Any guidance would be g
ctrl-d doesn't work?
Sent from my iRon
On Sep 19, 2014, at 17:51, "Thomas Schweikle" wrote:
Having following scripts:
bin/tc:
---
#!/usr/bin/bash
host=""
loop=0
conf=default
port=22
user=$USERNAME
cssh=1
cping=1
recon=0
while [ -n "$1" ]; do
case "$1" in
-f) conf="$2"; shift ;;
Having following scripts:
bin/tc:
---
#!/usr/bin/bash
host=""
loop=0
conf=default
port=22
user=$USERNAME
cssh=1
cping=1
recon=0
while [ -n "$1" ]; do
case "$1" in
-f) conf="$2"; shift ;;
-h) host="$2"; shift ;;
-l) loop=1;;
-nping) cping=0
On Sat, Apr 05, 2014 at 04:43:27PM -0400, Larry Hall (Cygwin) wrote:
>On 4/4/2014 3:35 PM, Ivan Todoroski wrote:
>> Cygwin DLL 1.7.28 32-bit
>> Windows 8.1 64-bit (build 6.3.9600)
>>
>> *Steps to reproduce*
>> 1) Open Cygwin bash prompt
>> 2) Type: ssh blargh # or any non-existent host
>> 3) Press
On 4/5/2014 4:43 PM, Larry Hall (Cygwin) wrote:
On 4/4/2014 3:35 PM, Ivan Todoroski wrote:
2) Type: ssh blargh # or any non-existent host
3) Press Ctrl-C immediately after that
On my machine, the Ctrl-C doesn't stop SSH from trying to look up the
non-existent host, it keeps going until it give
On 4/4/2014 3:35 PM, Ivan Todoroski wrote:
Cygwin DLL 1.7.28 32-bit
Windows 8.1 64-bit (build 6.3.9600)
*Steps to reproduce*
1) Open Cygwin bash prompt
2) Type: ssh blargh # or any non-existent host
3) Press Ctrl-C immediately after that
On my machine, the Ctrl-C doesn't stop SSH from trying t
Max Polk wrote on Saturday, April 5, 2014 16:50
>
> On 4/4/2014 3:35 PM, Ivan Todoroski wrote:
> > On my machine, the Ctrl-C doesn't stop SSH from trying to ...
>
> I believe console applications may require I/O to/from stdin/stdout/stderr
> for Control-C (or even Control-S / Control-Q for flow c
On 4/4/2014 3:35 PM, Ivan Todoroski wrote:
On my machine, the Ctrl-C doesn't stop SSH from trying to ...
I believe console applications may require I/O to/from
stdin/stdout/stderr for Control-C (or even Control-S / Control-Q for
flow control) to be noticed. In that period of time when there
Cygwin DLL 1.7.28 32-bit
Windows 8.1 64-bit (build 6.3.9600)
*Steps to reproduce*
1) Open Cygwin bash prompt
2) Type: ssh blargh # or any non-existent host
3) Press Ctrl-C immediately after that
On my machine, the Ctrl-C doesn't stop SSH from trying to look up the
non-existent host, it keeps goi
Am 13.01.2013 18:58, schrieb Thomas Wolff:
When I tried the recent snapshot (2013-01-11) it turned out that
Ctrl-C does not work anymore to interrupt a JVM program.
There had been a similar discussion last year
(http://cygwin.com/ml/cygwin/2012-07/msg00185.html) but it does not
seem to be the s
When I tried the recent snapshot (2013-01-11) it turned out that Ctrl-C
does not work anymore to interrupt a JVM program.
There had been a similar discussion last year
(http://cygwin.com/ml/cygwin/2012-07/msg00185.html) but it does not seem
to be the same problem;
in contrast to previous symptom
On Aug 7 18:21, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
>
> >> But I still need to see a practical example of
> >> running a M$ program like ping and stopping it with Ctrl+C
> >> without CMD (or another shell).
>
> > Why don't you just try it? On W7:
>
> Start Menu ->> Run... -> Ent
Greetings, Corinna Vinschen!
>> But I still need to see a practical example of
>> running a M$ program like ping and stopping it with Ctrl+C
>> without CMD (or another shell).
> Why don't you just try it? On W7:
Start Menu ->> Run... -> Enter "ping -t cygwin.com" -> Start Task Manager
->> Obser
On Aug 7 12:06, marco atzeri wrote:
> On 8/7/2012 10:20 AM, Andrey Repin wrote:
> >Greetings, marco atzeri!
> >
> >>a "windows console terminal" is cmd.exe, IMHO.
> >
> >No.
> >
> >>There are no other console in windows as standard installation.
> >
> >You're confusing terminal with shell.
> >CMD.
On 8/7/2012 10:20 AM, Andrey Repin wrote:
Greetings, marco atzeri!
a "windows console terminal" is cmd.exe, IMHO.
No.
There are no other console in windows as standard installation.
You're confusing terminal with shell.
CMD.EXE is a shell, same as BASH.
Console is a ... well, console.
-
Greetings, marco atzeri!
> a "windows console terminal" is cmd.exe, IMHO.
No.
> There are no other console in windows as standard installation.
You're confusing terminal with shell.
CMD.EXE is a shell, same as BASH.
Console is a ... well, console.
--
WBR,
Andrey Repin (anrdae...@freemail.ru)
On Fri, Aug 3, 2012 at 2:51 PM, Marcin Kielar wrote:
> 2012-08-03 18:23, Christopher Faylor:
>
>> I've uploaded a snapshot which should fix this issue.
>
>
> Confirmed to be working on snapshot 20120803:
>
> 1. Ctrl+C breaks ping loop - OK
> 2. Ctrl+C breaks Java process started through a `bat` fil
2012-08-03 18:23, Christopher Faylor:
I've uploaded a snapshot which should fix this issue.
Confirmed to be working on snapshot 20120803:
1. Ctrl+C breaks ping loop - OK
2. Ctrl+C breaks Java process started through a `bat` file - OK
It's likely that
we will now hear from the other contingen
On 08/03/2012 12:23 PM, Christopher Faylor wrote:
On Thu, Aug 02, 2012 at 09:32:09PM +0200, Marcin Kielar wrote:
Steps to reproduce:
1. Start cygwin using cygwin.bat
2. Run `ping -t google.com`
3. Try breaking it with Ctrl+C
Expected behaviur:
The ping breaks execution and the command prompt i
On Thu, Aug 02, 2012 at 09:32:09PM +0200, Marcin Kielar wrote:
>Steps to reproduce:
>
>1. Start cygwin using cygwin.bat
>2. Run `ping -t google.com`
>3. Try breaking it with Ctrl+C
>
>Expected behaviur:
>The ping breaks execution and the command prompt is shown and available
I've uploaded a snapsh
On Fri, Aug 03, 2012 at 04:07:39PM +0200, Corinna Vinschen wrote:
>On Aug 3 09:57, Christopher Faylor wrote:
>>This thread has it all. Affronted user, useless pile on, and now we
>>start to drift away from the actual subject.
>>
>>It's a little early here for popcorn but I'm tempted anyway.
>
>I'
On Aug 3 09:57, Christopher Faylor wrote:
> On Fri, Aug 03, 2012 at 03:51:30PM +0200, marco atzeri wrote:
> [...]
> >a "windows console terminal" is cmd.exe, IMHO.
> >There are no other console in windows as standard installation.
No, no, three times no.
Cmd.exe is just a console application usi
On Fri, Aug 03, 2012 at 09:57:16AM -0400, Christopher Faylor wrote:
>On Fri, Aug 03, 2012 at 03:51:30PM +0200, marco atzeri wrote:
>>On 8/3/2012 3:43 PM, Earnie Boyd wrote:
>>> On Thu, Aug 2, 2012 at 7:00 PM, Christopher Faylor wrote:
On Thu, Aug 02, 2012 at 09:32:09PM +0200, Marcin Kielar wro
On Fri, Aug 3, 2012 at 9:51 AM, marco atzeri wrote:
> On 8/3/2012 3:43 PM, Earnie Boyd wrote:
>>
>> On Thu, Aug 2, 2012 at 7:00 PM, Christopher Faylor wrote:
>>>
>>> On Thu, Aug 02, 2012 at 09:32:09PM +0200, Marcin Kielar wrote:
Steps to reproduce:
1. Start cygwin using cygwin.b
OK, I've found my example on how to resolve this issue:
Create a bash shell script and do the following:
#!/bin/bash
# Change the following to suit your application needs.
java -cp path.to.main.line &
function finalize() {
echo 'Terminating Application'
kill 0
}
trap finalize SIGINT
On Fri, Aug 03, 2012 at 03:51:30PM +0200, marco atzeri wrote:
>On 8/3/2012 3:43 PM, Earnie Boyd wrote:
>> On Thu, Aug 2, 2012 at 7:00 PM, Christopher Faylor wrote:
>>> On Thu, Aug 02, 2012 at 09:32:09PM +0200, Marcin Kielar wrote:
Steps to reproduce:
1. Start cygwin using cygwin.bat
On Fri, Aug 03, 2012 at 08:57:28AM -0400, Roger K. Wells wrote:
>On 08/03/2012 08:48 AM, Nellis, Kenneth wrote:
>> -Original Message-
>> From: Roger K. Wells
>>
>> Getting a PID & using kill just takes too long.
>> -END Original Message-
>>
>> pkill from the procps package might mi
On 8/3/2012 3:43 PM, Earnie Boyd wrote:
On Thu, Aug 2, 2012 at 7:00 PM, Christopher Faylor wrote:
On Thu, Aug 02, 2012 at 09:32:09PM +0200, Marcin Kielar wrote:
Steps to reproduce:
1. Start cygwin using cygwin.bat
2. Run `ping -t google.com`
3. Try breaking it with Ctrl+C
Expected behaviur:
T
On Thu, Aug 2, 2012 at 7:00 PM, Christopher Faylor wrote:
> On Thu, Aug 02, 2012 at 09:32:09PM +0200, Marcin Kielar wrote:
>>Steps to reproduce:
>>
>>1. Start cygwin using cygwin.bat
>>2. Run `ping -t google.com`
>>3. Try breaking it with Ctrl+C
>>
>>Expected behaviur:
>>The ping breaks execution a
On 08/03/2012 08:48 AM, Nellis, Kenneth wrote:
-Original Message-
From: Roger K. Wells
Getting a PID & using kill just takes too long.
-END Original Message-
pkill from the procps package might mitigate the pain.
--Ken Nellis
that too is a work around.
The point here is what is
On 08/02/2012 07:03 PM, Daniel Colascione wrote:
On 8/2/2012 4:00 PM, Christopher Faylor wrote:
On Thu, Aug 02, 2012 at 09:32:09PM +0200, Marcin Kielar wrote:
Steps to reproduce:
1. Start cygwin using cygwin.bat
2. Run `ping -t google.com`
3. Try breaking it with Ctrl+C
Expected behaviur:
The
-Original Message-
From: Roger K. Wells
Getting a PID & using kill just takes too long.
-END Original Message-
pkill from the procps package might mitigate the pain.
--Ken Nellis
On Thu, Aug 02, 2012 at 04:03:20PM -0700, Daniel Colascione wrote:
>On 8/2/2012 4:00 PM, Christopher Faylor wrote:
>> On Thu, Aug 02, 2012 at 09:32:09PM +0200, Marcin Kielar wrote:
>>> Steps to reproduce:
>>>
>>> 1. Start cygwin using cygwin.bat
>>> 2. Run `ping -t google.com`
>>> 3. Try breaking i
On 8/2/2012 4:00 PM, Christopher Faylor wrote:
> On Thu, Aug 02, 2012 at 09:32:09PM +0200, Marcin Kielar wrote:
>> Steps to reproduce:
>>
>> 1. Start cygwin using cygwin.bat
>> 2. Run `ping -t google.com`
>> 3. Try breaking it with Ctrl+C
>>
>> Expected behaviur:
>> The ping breaks execution and th
On Thu, Aug 02, 2012 at 09:32:09PM +0200, Marcin Kielar wrote:
>Steps to reproduce:
>
>1. Start cygwin using cygwin.bat
>2. Run `ping -t google.com`
>3. Try breaking it with Ctrl+C
>
>Expected behaviur:
>The ping breaks execution and the command prompt is shown and available
>
>Actual behaviour:
>N
On 08/02/2012 05:21 PM, Daniel Colascione wrote:
On 8/2/2012 2:02 PM, Roger K. Wells wrote:
On 08/02/2012 04:26 PM, Daniel Colascione wrote:
On 8/2/2012 12:32 PM, Marcin Kielar wrote:
Steps to reproduce:
1. Start cygwin using cygwin.bat
2. Run `ping -t google.com`
3. Try breaking it with Ctrl
On 8/2/2012 2:02 PM, Roger K. Wells wrote:
> On 08/02/2012 04:26 PM, Daniel Colascione wrote:
>> On 8/2/2012 12:32 PM, Marcin Kielar wrote:
>>> Steps to reproduce:
>>>
>>> 1. Start cygwin using cygwin.bat
>>> 2. Run `ping -t google.com`
>>> 3. Try breaking it with Ctrl+C
>> This problem arises from
On 08/02/2012 04:26 PM, Daniel Colascione wrote:
On 8/2/2012 12:32 PM, Marcin Kielar wrote:
Steps to reproduce:
1. Start cygwin using cygwin.bat
2. Run `ping -t google.com`
3. Try breaking it with Ctrl+C
This problem arises from Cygwin's use of CREATE_NEW_PROCESS_GROUP. From MSDN:
"When a pro
On 8/2/2012 12:32 PM, Marcin Kielar wrote:
> Steps to reproduce:
>
> 1. Start cygwin using cygwin.bat
> 2. Run `ping -t google.com`
> 3. Try breaking it with Ctrl+C
This problem arises from Cygwin's use of CREATE_NEW_PROCESS_GROUP. From MSDN:
"When a process is created with CREATE_NEW_PROCESS_GR
Steps to reproduce:
1. Start cygwin using cygwin.bat
2. Run `ping -t google.com`
3. Try breaking it with Ctrl+C
Expected behaviur:
The ping breaks execution and the command prompt is shown and available
Actual behaviour:
Nothing happens, ping loops until killed with `/usr/bin/kill -f PID`
Vari
Confirmed, the snapshot build appears to be working for me too. Thanks!
On Fri, Mar 2, 2012 at 1:57 PM, Kitchens wrote:
> I just ran the snapshot build, and CTRL+C appears to be working
> properly in /dev/consX
>
> --
> Kitchens
> .
>
> --
> Problem reports: http://cygwin.com/problems.html
I just ran the snapshot build, and CTRL+C appears to be working
properly in /dev/consX
--
Kitchens
.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/
On Mar 2 12:10, Corinna Vinschen wrote:
> On Mar 2 11:18, Corinna Vinschen wrote:
> > On Mar 1 19:22, Kitchens wrote:
> > > I've noticed this as well, and it seems to be a difference between
> > > /dev/consX and /dev/ptyX ttys. Mintty seems to work fine, whereas
> > > cmd.exe or Console2 (basica
On Mar 2 11:18, Corinna Vinschen wrote:
> On Mar 1 19:22, Kitchens wrote:
> > I've noticed this as well, and it seems to be a difference between
> > /dev/consX and /dev/ptyX ttys. Mintty seems to work fine, whereas
> > cmd.exe or Console2 (basically a cmd wrapper) cannot CTRL+C on the
> > command
On Mar 1 19:22, Kitchens wrote:
> I've noticed this as well, and it seems to be a difference between
> /dev/consX and /dev/ptyX ttys. Mintty seems to work fine, whereas
> cmd.exe or Console2 (basically a cmd wrapper) cannot CTRL+C on the
> command line to abort it. Ctrl+C does, however, issue a SI
I've noticed this as well, and it seems to be a difference between
/dev/consX and /dev/ptyX ttys. Mintty seems to work fine, whereas
cmd.exe or Console2 (basically a cmd wrapper) cannot CTRL+C on the
command line to abort it. Ctrl+C does, however, issue a SIGINT for a
running process.
This issue h
I use vi mode (set -o vi) in bash. A couple of days ago I updated my
cygwin installation and now I'm no longer able to use ctrl-c to abort
command line editing. Specifically, while typing a command or editing
a previous command from the history, it used to be possible to discard
the command text
Scott Wells hotmail.com> writes:
> I'll keep playing with this but, assuming it works as it seems to, this
> is great!
Okay, scratch that...while the simple build seemed to be working properly when
run through the shell script, I tried running a Swing-based sample program and
CTRL-C killed the t
Scott Wells hotmail.com> writes:
> Hi. I'm a longtime cygwin user (since it was gnu-win32) who has struggled to
> solve one particular long-standing disconnect between cygwin and native Win32
> command-line utilities, notably that unless you're using a cygwin shell from a
> cmd.exe window (or to
Hi. I'm a longtime cygwin user (since it was gnu-win32) who has struggled to
solve one particular long-standing disconnect between cygwin and native Win32
command-line utilities, notably that unless you're using a cygwin shell from a
cmd.exe window (or tools like Console2 that effectively co-opt t
Christopher Faylor wrote:
According to Alex Goldman on 7/21/2005 2:49 AM:
On Linux, after I start a program that consumes 100% of CPU time, I can
usually terminate it just by typing Ctrl-C. This is very convenient to
me as a developer. However, using Cygwin in the same situation, the
shell
On Thu, 21 Jul 2005, Alex Goldman wrote:
> On Linux, after I start a program that consumes 100% of CPU time, I
> can usually terminate it just by typing Ctrl-C. This is very
> convenient to me as a developer. However, using Cygwin in the same
> situation, the shell becomes "bash (Not Responding)",
My tty settings are fine. I run Rxvt by calling
C:
chdir C:\cygwin\bin
set CYGWIN=codepage:oem tty binmode title
rxvt -sl 1000 -e bash --login -i
Looking into this more closely, I noticed that the problem occurs for
programs compiled using the free MSVC++ Toolkit 2003, but not GCC.
I think you
On Thu, Jul 21, 2005 at 06:06:39AM -0600, Eric Blake wrote:
>According to Alex Goldman on 7/21/2005 2:49 AM:
>>On Linux, after I start a program that consumes 100% of CPU time, I can
>>usually terminate it just by typing Ctrl-C. This is very convenient to
>>me as a developer. However, using Cygwi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Alex Goldman on 7/21/2005 2:49 AM:
> On Linux, after I start a program that consumes 100% of CPU time, I
> can usually terminate it just by typing Ctrl-C. This is very
> convenient to me as a developer. However, using Cygwin in the same
>
On Linux, after I start a program that consumes 100% of CPU time, I
can usually terminate it just by typing Ctrl-C. This is very
convenient to me as a developer. However, using Cygwin in the same
situation, the shell becomes "bash (Not Responding)", and I have to
invoke the process manager and kill
57 matches
Mail list logo
