RE: Control-C not working?
On 12 December 2007 18:16, Paul Sterk wrote: Hi, I am a cygwin newbie. I installed it this past August. The version on the installer is '2.573.2.2'. That's the version of the installer; unless reporting a bug in the installer, it's not useful, as it doesn't tell you anything about the version of cygwin that the installer installed for you, which is independent. My problem is the Control-C does not kill a running process. Why is that? Maybe your ctrl key is broken? Is there a way to enable this? There isn't any switch or flag; ctrl-c is just meant to work - and indeed does, at least for me. What shell and terminal are you using? cheers, DaveK -- Can't think of a witty .sigline today -- 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/
Re: Control-c not working in rxvt
On Sat, 28 Feb 2004, Chuck Irvine wrote: Please forgive me if this is a basic question, but I've searched google and the cygwin mail archives and can't find the answer. (Actually, someone asked the same question on the mailing list, but no one responded.) While using rxvt, I can't use control-c to exit a running program, i.e. pressing control-c does nothing. From the default bash shell, this works fine. I would appreciate your help. Thanks. Chuck Chuck, Please review Problem reports: http://cygwin.com/problems.html and try asking your question again. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton -- 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/
RE: Control-c not working in rxvt (for exiting jboss server)
When I start Jboss server from rxvt, I cannot exit, that is, shutdown the server, using Control-c. If I start the server from the normal cygwin bash prompt, that is, cywin.bat, control-c shuts down the server. Control-c from rxvt in other contexts does seem to work, for example, if I invoke ping -n 100 localhost control-c does cause an exit. Cygcheck output attached. Thanks Chuck -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Igor Pechtchanski Sent: Saturday, February 28, 2004 10:44 AM To: Chuck Irvine Cc: [EMAIL PROTECTED] Subject: Re: Control-c not working in rxvt On Sat, 28 Feb 2004, Chuck Irvine wrote: Please forgive me if this is a basic question, but I've searched google and the cygwin mail archives and can't find the answer. (Actually, someone asked the same question on the mailing list, but no one responded.) While using rxvt, I can't use control-c to exit a running program, i.e. pressing control-c does nothing. From the default bash shell, this works fine. I would appreciate your help. Thanks. Chuck Chuck, Please review Problem reports: http://cygwin.com/problems.html and try asking your question again. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ [EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_ [EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton -- 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/ cygcheck.out Description: Binary data -- 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/
Re: Control-c not working in rxvt (for exiting jboss server)
Chuck Irvine wrote:
When I start Jboss server from rxvt, I cannot exit, that is, shutdown
the server, using Control-c. If I start the server from the normal
cygwin bash prompt, that is, cywin.bat, control-c shuts down the server.
Control-c from rxvt in other contexts does seem to work, for example, if
I invoke ping -n 100 localhost control-c does cause an exit. Cygcheck
output attached. Thanks
Chuck
Chuck,
I would start by trying the latest snapshot. Cygwin 1.5.7 has some
problems with signal handling.
If you start JBoss with a script, you could also try changing it from
/bin/sh to /bin/bash or vice versa, since I seem to recall the two shells
handling signals differently in 1.5.7. That might not be true any longer,
though, with the latest ash.
Finally, you can try to explicitly kill the Jboss (Java?) process using
something like the following.
---
#!/bin/bash
enTrapSIGINT () {
kill $child_pid;
exit;
}
trap enTrapSIGINT 2
startJboss
child_pid = $!
wait
Dave
--
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/
RE: Control-c not working in rxvt (for exiting jboss server)
Dave,
I tried changing the jboss startup script to use /usr/bin/bash instead
of /bin/sh and that worked pretty well. When I hit control-c, the
jboss server does shut down. However, the normal logging sent to
standard out showing the progress of the shutdown does not come through.
Not sure what to make of that - maybe it's doing a kill -9? Still,
right now, I deem this an improvement.
I'm a little hesitant to go to the latest snapshot since I rely on
cygwin for many things. Do you think it is as safe as the current
version?
Jboss comes with a shutdown script. I just wanted the convenience of
shutting down via control-c.
Thanks for your help.
Chuck
-Original Message-
From: David Rothenberger [mailto:[EMAIL PROTECTED]
Sent: Saturday, February 28, 2004 12:41 PM
To: Chuck Irvine
Cc: [EMAIL PROTECTED]
Subject: Re: Control-c not working in rxvt (for exiting jboss server)
Chuck Irvine wrote:
When I start Jboss server from rxvt, I cannot exit, that
is, shutdown
the server, using Control-c. If I start the server from the normal
cygwin bash prompt, that is, cywin.bat, control-c shuts down the
server. Control-c from rxvt in other contexts does seem to
work, for
example, if I invoke ping -n 100 localhost control-c does
cause an
exit. Cygcheck output attached. Thanks
Chuck
Chuck,
I would start by trying the latest snapshot. Cygwin 1.5.7 has some
problems with signal handling.
If you start JBoss with a script, you could also try changing it from
/bin/sh to /bin/bash or vice versa, since I seem to recall
the two shells
handling signals differently in 1.5.7. That might not be
true any longer,
though, with the latest ash.
Finally, you can try to explicitly kill the Jboss (Java?)
process using
something like the following.
---
#!/bin/bash
enTrapSIGINT () {
kill $child_pid;
exit;
}
trap enTrapSIGINT 2
startJboss
child_pid = $!
wait
Dave
--
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/
RE: Control-c not working in rxvt (for exiting jboss server)
Chuck,
If you wish to get a clean shutdown, *do not* rely on Cygwin signals
unless you're sure that the program can handle them properly. I suggest
looking at the Cygwin sources to find out exactly what a SIGINT gets
turned into for Windows processes. Most likely it's doing exactly what
you inferred - a TerminateProcess (the Windows equivalent of kill -9)
-- I don't have the sources handy to check right now. Looking at the
parts of the output of strace bash dealing with signal delivery might
also prove instructive.
Or, as Dave mentioned, you can always use the 'trap' command to invoke the
JBoss shutdown script on SIGINT.
Igor
On Sat, 28 Feb 2004, Chuck Irvine wrote:
Dave,
I tried changing the jboss startup script to use /usr/bin/bash instead
of /bin/sh and that worked pretty well. When I hit control-c, the
jboss server does shut down. However, the normal logging sent to
standard out showing the progress of the shutdown does not come through.
Not sure what to make of that - maybe it's doing a kill -9? Still,
right now, I deem this an improvement.
I'm a little hesitant to go to the latest snapshot since I rely on
cygwin for many things. Do you think it is as safe as the current
version?
Jboss comes with a shutdown script. I just wanted the convenience of
shutting down via control-c.
Thanks for your help.
Chuck
-Original Message-
From: David Rothenberger [mailto:[EMAIL PROTECTED]
Sent: Saturday, February 28, 2004 12:41 PM
To: Chuck Irvine
Cc: [EMAIL PROTECTED]
Subject: Re: Control-c not working in rxvt (for exiting jboss server)
Chuck Irvine wrote:
When I start Jboss server from rxvt, I cannot exit, that is, shutdown
the server, using Control-c. If I start the server from the normal
cygwin bash prompt, that is, cywin.bat, control-c shuts down the
server. Control-c from rxvt in other contexts does seem to work, for
example, if I invoke ping -n 100 localhost control-c does cause an
exit. Cygcheck output attached. Thanks
Chuck
Chuck,
I would start by trying the latest snapshot. Cygwin 1.5.7 has some
problems with signal handling.
If you start JBoss with a script, you could also try changing it from
/bin/sh to /bin/bash or vice versa, since I seem to recall
the two shells
handling signals differently in 1.5.7. That might not be
true any longer,
though, with the latest ash.
Finally, you can try to explicitly kill the Jboss (Java?)
process using
something like the following.
---
#!/bin/bash
enTrapSIGINT () {
kill $child_pid;
exit;
}
trap enTrapSIGINT 2
startJboss
child_pid = $!
wait
Dave
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED]
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster. -- Patrick Naughton
--
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/
Re: Control-c not working in rxvt (for exiting jboss server)
Chuck Irvine wrote: I'm a little hesitant to go to the latest snapshot since I rely on cygwin for many things. Do you think it is as safe as the current version? I think it's much safer, actually. I've been using the latest snapshot since it was released and believe it to be the best since before 1.5.7. Jboss comes with a shutdown script. I just wanted the convenience of shutting down via control-c. How about invoking the shutdown script from the signal handler in the start script (enTrapSIGINT in my example). That way you should get a clean shutdown from the convenience of a Ctrl-C. If you do that, you may want to clear the signal handler from within enTrapSIGINT so that if the shutdown script hangs, you can use Ctrl-C to abort the script. Dave P.S. Please ensure your mailer honors the Reply-To header so you don't reply directly to me. P.P.S. Please adjust your mailer to exclude raw email addresses from your quoted responses. No need to make the job of spam harvesters any easier. -- 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/
RE: Control-c not working in rxvt (for exiting jboss server)
At 02:08 PM 2/28/2004, Chuck Irvine you wrote: I'm a little hesitant to go to the latest snapshot since I rely on cygwin for many things. Do you think it is as safe as the current version? What does that mean? What makes the current version safe? You are implying something here by your vagueness. The implications, more than likely, aren't synonymous with your intent. But you need to be more clear with your question if you expect to get any kind of meaningful answer. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/
RE: Control-c not working in rxvt (for exiting jboss server)
Larry, I see that I've caused you some concern. Let me be more specific. Not being familiar with Cygwin snapshots, I was tending to equate the term with what might go by the name daily builds in other projects. Folks are often warned that these are less stable then the current stable release and that care should be exercised. Chuck -Original Message- From: Larry Hall Sent: Saturday, February 28, 2004 2:39 PM To: Chuck Irvine Cc: [EMAIL PROTECTED] Subject: RE: Control-c not working in rxvt (for exiting jboss server) At 02:08 PM 2/28/2004, Chuck Irvine you wrote: I'm a little hesitant to go to the latest snapshot since I rely on cygwin for many things. Do you think it is as safe as the current version? What does that mean? What makes the current version safe? You are implying something here by your vagueness. The implications, more than likely, aren't synonymous with your intent. But you need to be more clear with your question if you expect to get any kind of meaningful answer. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/
Re: Control-c not working in rxvt (for exiting jboss server)
On Sat, Feb 28, 2004 at 03:20:56PM -0600, Chuck Irvine wrote: I see that I've caused you some concern. Let me be more specific. Not being familiar with Cygwin snapshots, I was tending to equate the term with what might go by the name daily builds in other projects. Folks are often warned that these are less stable then the current stable release and that care should be exercised. Your understanding is correct. However as we converge on a new release, the snapshots do become more stable. And, sometimes, as for the last few months, we do enter periods of instability in cygwin where snapshots are consistently better than the last release. The recent period of instability is due to my efforts to implement multi-threaded signal handling into cygwin. This was done for a Red Hat contract (even though I still ended up doing this basically for gratis in my spare time). The need for development hit during a time when there were also some other destabilizing changes in the cygwin code base. In a perfect world, I would have spaced out the releases to give each bit of new functionality time to settle down. Unfortunately events did not allow this. Anyway, the most recent snapshots should be better than 1.5.7. There are still a couple of reported problems but I don't think there are any real regressions in functionality. 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/
RE: Control-c not working in rxvt (for exiting jboss server)
I think Chris's response sums up the current state of the Cygwin DLL quite nicely and properly sets the expectations for recent snapshots. Obviously, in general, snapshot volatility can vary. People who try snapshots generally shouldn't expect that the snapshot will perform better than a release in every way. It could even not work at all. But the warnings are really raised to make sure people are aware that things might not work with a snapshot. It's setting a level of expectation appropriately so there's no great surprise if something isn't working quite right. It's not meant to imply that snapshots are somehow inherently dangerous and that using one, even if it ends up being completely broken, is an unrecoverable event. It just means you have to be prepared to fall back to the current release if things don't work out. Whether my comments make you more or less willing to try a snapshot now or in general, I don't know. Obviously, the choice is up to you. I'm not trying to force you to use one, if that would even be possible somehow. But I wanted to clarify this point for others who might be unsure of the reasons behind the warnings about snapshots. Larry At 04:20 PM 2/28/2004, Chuck Irvine you wrote: Larry, I see that I've caused you some concern. Let me be more specific. Not being familiar with Cygwin snapshots, I was tending to equate the term with what might go by the name daily builds in other projects. Folks are often warned that these are less stable then the current stable release and that care should be exercised. Chuck -Original Message- From: Larry Hall Sent: Saturday, February 28, 2004 2:39 PM To: Chuck Irvine Cc: [EMAIL PROTECTED] Subject: RE: Control-c not working in rxvt (for exiting jboss server) At 02:08 PM 2/28/2004, Chuck Irvine you wrote: I'm a little hesitant to go to the latest snapshot since I rely on cygwin for many things. Do you think it is as safe as the current version? What does that mean? What makes the current version safe? You are implying something here by your vagueness. The implications, more than likely, aren't synonymous with your intent. But you need to be more clear with your question if you expect to get any kind of meaningful answer. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/
