* Control-c not working in rxvt
@ 2004-02-28 16:43 Chuck Irvine
2004-02-28 18:33 ` Igor Pechtchanski
0 siblings, 1 reply; 11+ messages in thread
From: Chuck Irvine @ 2004-02-28 16:43 UTC (permalink / raw)
To: Cygwin
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
--
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/
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Control-c not working in rxvt
2004-02-28 16:43 Control-c not working in rxvt Chuck Irvine
@ 2004-02-28 18:33 ` Igor Pechtchanski
2004-02-28 18:46 ` Control-c not working in rxvt (for exiting jboss server) Chuck Irvine
0 siblings, 1 reply; 11+ messages in thread
From: Igor Pechtchanski @ 2004-02-28 18:33 UTC (permalink / raw)
To: Chuck Irvine; +Cc: cygwin
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/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,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/
^ permalink raw reply [flat|nested] 11+ messages in thread
* RE: Control-c not working in rxvt (for exiting jboss server)
2004-02-28 18:33 ` Igor Pechtchanski
@ 2004-02-28 18:46 ` Chuck Irvine
2004-02-28 19:24 ` David Rothenberger
0 siblings, 1 reply; 11+ messages in thread
From: Chuck Irvine @ 2004-02-28 18:46 UTC (permalink / raw)
To: cygwin
[-- Attachment #1: Type: text/plain, Size: 1951 bytes --]
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: cygwin-owner@cygwin.com
> [mailto:cygwin-owner@cygwin.com] On Behalf Of Igor Pechtchanski
> Sent: Saturday, February 28, 2004 10:44 AM
> To: Chuck Irvine
> Cc: cygwin@cygwin.com
> 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/
> |\ _,,,---,,_ pechtcha@cs.nyu.edu
> ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
> |,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/
>
>
[-- Attachment #2: cygcheck.out --]
[-- Type: application/octet-stream, Size: 16168 bytes --]
Cygwin Win95/NT Configuration Diagnostics
Current System Time: Sat Feb 28 11:18:18 2004
Windows XP Professional Ver 5.1 Build 2600 Service Pack 1
Path: c:\apps\j2sdk1.4.2_02\bin
c:\apps\jakarta-ant-1.5.1\bin
c:\apps\emacs-21.2\bin
C:\cygwin\home\chuck\bin
C:\cygwin\usr\local\bin
C:\cygwin\bin
C:\cygwin\bin
c:\apps\cvs
c:\apps\j2sdk1.4.2_02\bin
c:\WINDOWS\system32
c:\WINDOWS
c:\WINDOWS\System32\Wbem
c:\WINDOWS\System32
c:\Program Files\Common Files\Roxio Shared\DLLShared
C:\cygwin\usr\sbin
C:\cygwin\bin
.
C:\cygwin\usr\sbin
Output from C:\cygwin\bin\id.exe (nontsec)
UID: 1008(Chuck) GID: 513(None)
513(None)
Output from C:\cygwin\bin\id.exe (ntsec)
UID: 1008(Chuck) GID: 513(None)
513(None) 544(Administrators)
545(Users)
SysDir: C:\WINDOWS\System32
WinDir: C:\WINDOWS
HOME = `c:\Documents and Settings\Chuck\My Documents'
MAKE_MODE = `unix'
PWD = `/apps/jboss-3.2.3/bin'
USER = `Chuck'
cygwin = `true'
ALLUSERSPROFILE = `C:\Documents and Settings\All Users'
ANT_HOME = `/apps/jakarta-ant-1.5.1'
APPDATA = `C:\Documents and Settings\Chuck\Application Data'
CATALINA_HOME = `/apps/jakarta-tomcat-4.1.18'
CLIENTNAME = `Console'
COLORFGBG = `10;default;0'
COLORTERM = `rxvt-xpm'
COMMONPROGRAMFILES = `C:\Program Files\Common Files'
COMPUTERNAME = `RAY'
COMSPEC = `C:\WINDOWS\system32\cmd.exe'
CVSROOT = `/cvsroot'
DISPLAY = `:0'
EMACS_HOME = `/apps/emacs-21.2'
HOMEDRIVE = `C:'
HOMEPATH = `\Documents and Settings\Chuck'
JAVA_HOME = `/apps/j2sdk1.4.2_02'
LOGONSERVER = `\\RAY'
MANPATH = `:/usr/ssl/man'
NUMBER_OF_PROCESSORS = `1'
OLDPWD = `/chuck'
OS = `Windows_NT'
PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH'
PROCESSOR_ARCHITECTURE = `x86'
PROCESSOR_IDENTIFIER = `x86 Family 15 Model 2 Stepping 7, GenuineIntel'
PROCESSOR_LEVEL = `15'
PROCESSOR_REVISION = `0207'
PROGRAMFILES = `C:\Program Files'
PROMPT = `$P$G'
PS1 = `\W$ '
SESSIONNAME = `Console'
SHLVL = `1'
SYSTEMDRIVE = `C:'
SYSTEMROOT = `C:\WINDOWS'
TEMP = `C:\cygwin\tmp'
TERM = `xterm'
TMP = `c:\DOCUME~1\Chuck\LOCALS~1\Temp'
TMPDIR = `C:\cygwin\tmp'
USERDOMAIN = `RAY'
USERNAME = `Chuck'
USERPROFILE = `C:\Documents and Settings\Chuck'
WINDIR = `C:\WINDOWS'
WINDOWID = `168047616'
_ = `/usr/bin/cygcheck'
HKEY_CURRENT_USER\Software\Cygnus Solutions
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2
(default) = `/cygdrive'
cygdrive flags = 0x00000020
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2
(default) = `/cygdrive'
cygdrive flags = 0x00000020
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/
(default) = `C:\cygwin'
flags = 0x00000008
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/apps
(default) = `c:\apps'
flags = 0x00000008
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/chuck
(default) = `c:\Documents and Settings\Chuck\My Documents'
flags = 0x00000008
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/cvshome
(default) = `c:\cvshome'
flags = 0x00000008
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/cvsroot
(default) = `c:\cvsroot'
flags = 0x00000008
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/src
(default) = `c:\src'
flags = 0x00000008
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/bin
(default) = `C:\cygwin/bin'
flags = 0x00000008
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/lib
(default) = `C:\cygwin/lib'
flags = 0x00000008
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options
a: fd N/A N/A
c: hd NTFS 57184Mb 36% CP CS UN PA FC
d: cd UDF 29Mb 100% CS UN 040226_2325
e: cd CDFS 325Mb 100% CS UN Timeshock!
f: hd FAT 31Mb 18% CP UN
. /cygdrive user textmode,cygdrive
C:\cygwin / system textmode
c:\apps /apps system textmode
c:\Documents and Settings\Chuck\My Documents /chuck system textmode
c:\cvshome /cvshome system textmode
c:\cvsroot /cvsroot system textmode
c:\src /src system textmode
C:\cygwin/bin /usr/bin system textmode
C:\cygwin/lib /usr/lib system textmode
. /cygdrive system textmode,cygdrive
Found: C:\cygwin\bin\awk.exe
Found: C:\cygwin\bin\bash.exe
Found: C:\cygwin\bin\cat.exe
Found: C:\cygwin\bin\cp.exe
Not Found: cpp (good!)
Found: C:\cygwin\bin\find.exe
Not Found: gcc
Not Found: gdb
Found: C:\cygwin\bin\grep.exe
Not Found: ld
Found: C:\cygwin\bin\ls.exe
Found: C:\cygwin\bin\make.exe
Found: C:\cygwin\bin\mv.exe
Found: C:\cygwin\bin\rm.exe
Found: C:\cygwin\bin\sed.exe
Found: C:\cygwin\bin\sh.exe
Found: C:\cygwin\bin\tar.exe
61k 2003/08/09 C:\cygwin\bin\cygbz2-1.dll - os=4.0 img=1.0 sys=4.0
"cygbz2-1.dll" v0.0 ts=2003/8/9 1:35
7k 2003/10/19 C:\cygwin\bin\cygcrypt-0.dll - os=4.0 img=1.0 sys=4.0
"cygcrypt-0.dll" v0.0 ts=2003/10/19 2:57
842k 2003/09/30 C:\cygwin\bin\cygcrypto-0.9.7.dll - os=4.0 img=1.0 sys=4.0
"cygcrypto-0.9.7.dll" v0.0 ts=2003/9/30 11:49
22k 2004/02/10 C:\cygwin\bin\cygcygipc-2.dll - os=4.0 img=1.0 sys=4.0
"cygcygipc-2.dll" v0.0 ts=2004/2/9 20:48
380k 2002/07/24 C:\cygwin\bin\cygdb-3.1.dll - os=4.0 img=1.0 sys=4.0
"cygdb-3.1.dll" v0.0 ts=2002/7/24 11:24
831k 2003/09/20 C:\cygwin\bin\cygdb-4.1.dll - os=4.0 img=1.0 sys=4.0
"cygdb-4.1.dll" v0.0 ts=2003/9/20 16:51
487k 2002/07/24 C:\cygwin\bin\cygdb_cxx-3.1.dll - os=4.0 img=1.0 sys=4.0
"cygdb_cxx-3.1.dll" v0.0 ts=2002/7/24 11:25
1080k 2003/09/20 C:\cygwin\bin\cygdb_cxx-4.1.dll - os=4.0 img=1.0 sys=4.0
"cygdb_cxx-4.1.dll" v0.0 ts=2003/9/20 16:53
45k 2001/04/25 C:\cygwin\bin\cygform5.dll - os=4.0 img=1.0 sys=4.0
"cygform5.dll" v0.0 ts=2001/4/25 0:28
35k 2002/01/09 C:\cygwin\bin\cygform6.dll - os=4.0 img=1.0 sys=4.0
"cygform6.dll" v0.0 ts=2002/1/9 0:03
48k 2003/08/09 C:\cygwin\bin\cygform7.dll - os=4.0 img=1.0 sys=4.0
"cygform7.dll" v0.0 ts=2003/8/9 4:25
28k 2003/07/20 C:\cygwin\bin\cyggdbm-3.dll - os=4.0 img=1.0 sys=4.0
"cyggdbm-3.dll" v0.0 ts=2003/7/20 2:58
30k 2003/08/11 C:\cygwin\bin\cyggdbm-4.dll - os=4.0 img=1.0 sys=4.0
"cyggdbm-4.dll" v0.0 ts=2003/8/10 21:12
19k 2003/03/22 C:\cygwin\bin\cyggdbm.dll - os=4.0 img=1.0 sys=4.0
"cyggdbm.dll" v0.0 ts=2002/2/19 21:05
15k 2003/07/20 C:\cygwin\bin\cyggdbm_compat-3.dll - os=4.0 img=1.0 sys=4.0
"cyggdbm_compat-3.dll" v0.0 ts=2003/7/20 3:00
15k 2003/08/11 C:\cygwin\bin\cyggdbm_compat-4.dll - os=4.0 img=1.0 sys=4.0
"cyggdbm_compat-4.dll" v0.0 ts=2003/8/10 21:13
69k 2003/08/10 C:\cygwin\bin\cyggettextlib-0-12-1.dll - os=4.0 img=1.0 sys=4.0
"cyggettextlib-0-12-1.dll" v0.0 ts=2003/8/10 17:10
12k 2003/08/10 C:\cygwin\bin\cyggettextpo-0.dll - os=4.0 img=1.0 sys=4.0
"cyggettextpo-0.dll" v0.0 ts=2003/8/10 17:11
134k 2003/08/10 C:\cygwin\bin\cyggettextsrc-0-12-1.dll - os=4.0 img=1.0 sys=4.0
"cyggettextsrc-0-12-1.dll" v0.0 ts=2003/8/10 17:10
17k 2001/06/28 C:\cygwin\bin\cyghistory4.dll - os=4.0 img=1.0 sys=4.0
"cyghistory4.dll" v0.0 ts=2001/1/6 22:34
29k 2003/08/10 C:\cygwin\bin\cyghistory5.dll - os=4.0 img=1.0 sys=4.0
"cyghistory5.dll" v0.0 ts=2003/8/10 18:16
958k 2003/08/10 C:\cygwin\bin\cygiconv-2.dll - os=4.0 img=1.0 sys=4.0
"cygiconv-2.dll" v0.0 ts=2003/8/10 15:57
22k 2001/12/13 C:\cygwin\bin\cygintl-1.dll - os=4.0 img=1.0 sys=4.0
"cygintl-1.dll" v0.0 ts=2001/12/13 3:28
37k 2003/08/10 C:\cygwin\bin\cygintl-2.dll - os=4.0 img=1.0 sys=4.0
"cygintl-2.dll" v0.0 ts=2003/8/10 16:50
26k 2001/04/25 C:\cygwin\bin\cygmenu5.dll - os=4.0 img=1.0 sys=4.0
"cygmenu5.dll" v0.0 ts=2001/4/25 0:27
20k 2002/01/09 C:\cygwin\bin\cygmenu6.dll - os=4.0 img=1.0 sys=4.0
"cygmenu6.dll" v0.0 ts=2002/1/9 0:03
29k 2003/08/09 C:\cygwin\bin\cygmenu7.dll - os=4.0 img=1.0 sys=4.0
"cygmenu7.dll" v0.0 ts=2003/8/9 4:25
156k 2001/04/25 C:\cygwin\bin\cygncurses++5.dll - os=4.0 img=1.0 sys=4.0
"cygncurses++5.dll" v0.0 ts=2001/4/25 0:29
175k 2002/01/09 C:\cygwin\bin\cygncurses++6.dll - os=4.0 img=1.0 sys=4.0
"cygncurses++6.dll" v0.0 ts=2002/1/9 0:03
226k 2001/04/25 C:\cygwin\bin\cygncurses5.dll - os=4.0 img=1.0 sys=4.0
"cygncurses5.dll" v0.0 ts=2001/4/25 0:17
202k 2002/01/09 C:\cygwin\bin\cygncurses6.dll - os=4.0 img=1.0 sys=4.0
"cygncurses6.dll" v0.0 ts=2002/1/9 0:03
224k 2003/08/09 C:\cygwin\bin\cygncurses7.dll - os=4.0 img=1.0 sys=4.0
"cygncurses7.dll" v0.0 ts=2003/8/9 4:24
15k 2001/04/25 C:\cygwin\bin\cygpanel5.dll - os=4.0 img=1.0 sys=4.0
"cygpanel5.dll" v0.0 ts=2001/4/25 0:27
12k 2002/01/09 C:\cygwin\bin\cygpanel6.dll - os=4.0 img=1.0 sys=4.0
"cygpanel6.dll" v0.0 ts=2002/1/9 0:03
19k 2003/08/09 C:\cygwin\bin\cygpanel7.dll - os=4.0 img=1.0 sys=4.0
"cygpanel7.dll" v0.0 ts=2003/8/9 4:24
62k 2003/12/11 C:\cygwin\bin\cygpcre-0.dll - os=4.0 img=1.0 sys=4.0
"cygpcre-0.dll" v0.0 ts=2003/12/11 11:01
63k 2003/04/11 C:\cygwin\bin\cygpcre.dll - os=4.0 img=1.0 sys=4.0
"cygpcre.dll" v0.0 ts=2003/4/11 3:31
9k 2003/12/11 C:\cygwin\bin\cygpcreposix-0.dll - os=4.0 img=1.0 sys=4.0
"cygpcreposix-0.dll" v0.0 ts=2003/12/11 11:01
61k 2003/04/11 C:\cygwin\bin\cygpcreposix.dll - os=4.0 img=1.0 sys=4.0
"cygpcreposix.dll" v0.0 ts=2003/4/11 3:31
1049k 2003/11/07 C:\cygwin\bin\cygperl5_8_2.dll - os=4.0 img=1.0 sys=4.0
"cygperl5_8_2.dll" v0.0 ts=2003/11/7 5:08
22k 2002/06/09 C:\cygwin\bin\cygpopt-0.dll - os=4.0 img=1.0 sys=4.0
"cygpopt-0.dll" v0.0 ts=2002/6/9 0:45
108k 2001/06/28 C:\cygwin\bin\cygreadline4.dll - os=4.0 img=1.0 sys=4.0
"cygreadline4.dll" v0.0 ts=2001/1/6 22:34
148k 2003/08/10 C:\cygwin\bin\cygreadline5.dll - os=4.0 img=1.0 sys=4.0
"cygreadline5.dll" v0.0 ts=2003/8/10 18:16
171k 2003/09/30 C:\cygwin\bin\cygssl-0.9.7.dll - os=4.0 img=1.0 sys=4.0
"cygssl-0.9.7.dll" v0.0 ts=2003/9/30 11:49
61k 2003/12/04 C:\cygwin\bin\cygz.dll - os=4.0 img=1.0 sys=4.0
"cygz.dll" v0.0 ts=2003/12/3 21:03
1083k 2004/01/31 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
"cygwin1.dll" v0.0 ts=2004/1/30 18:32
Cygwin DLL version info:
DLL version: 1.5.7
DLL epoch: 19
DLL bad signal mask: 19005
DLL old termios: 5
DLL malloc env: 28
API major: 0
API minor: 109
Shared data: 3
DLL identifier: cygwin1
Mount registry: 2
Cygnus registry name: Cygnus Solutions
Cygwin registry name: Cygwin
Program options name: Program Options
Cygwin mount registry name: mounts v2
Cygdrive flags: cygdrive flags
Cygdrive prefix: cygdrive prefix
Cygdrive default prefix:
Build date: Fri Jan 30 19:32:04 EST 2004
CVS tag: cr-0x9e
Shared id: cygwin1S3
Cygwin Package Information
Last downloaded files to: C:\Documents and Settings\Chuck\My Documents\CygwinSetup\cygwinPackage
Last downloaded files from: ftp://ftp.nas.nasa.gov/mirrors/cygwin.com/pub/cygwin
Package Version
_update-info-dir 00227-1
ash 20040127-1
base-files 2.6-1
base-passwd 1.1-1
bash 2.05b-16
bzip2 1.0.2-5
check 0.8.4-1
clear 1.0-1
crypt 1.1-1
cvs 1.11.6-3
cygipc 2.03-2
cygrunsrv 0.98-1
cygutils 1.2.4-1
cygwin 1.5.7-1
cygwin-doc 1.3-7
diff 1.0-1
diffutils 2.8.4-1
editrights 1.01-1
fetchmail 6.2.5-2
fileutils 4.1-2
findutils 4.1.7-4
gawk 3.1.3-4
gdbm 1.8.3-7
grep 2.5-1
groff 1.18.1-2
gzip 1.3.5-1
inetutils 1.3.2-26
less 381-1
libbz2_1 1.0.2-5
libdb3.1 3.1.17-2
libdb4.1 4.1.25-1
libgdbm 1.8.0-5
libgdbm-devel 1.8.3-7
libgdbm3 1.8.3-3
libgdbm4 1.8.3-7
libgettextpo0 0.12.1-3
libiconv2 1.9.1-3
libintl1 0.10.40-1
libintl2 0.12.1-3
libncurses5 5.2-1
libncurses6 5.2-8
libncurses7 5.3-4
libpcre 4.1-1
libpcre0 4.5-1
libpopt0 1.6.4-4
libreadline4 4.1-2
libreadline5 4.3-5
login 1.9-7
make 3.80-1
man 1.5k-2
mc 4.6.0-4
mktemp 1.5-3
mutt 1.4.1-2
ncurses 5.3-4
newlib-man 20020801
openssl 0.9.7c-1
patch 2.5.8-8
pcre 4.5-1
pcre-doc 4.5-1
pdksh 5.2.14-3
perl 5.8.2-1
postgresql 7.4.1-3
readline 4.3-5
rxvt 2.7.10-3
sed 4.0.8-1
sh-utils 2.0.15-4
ssmtp 2.60.4-3
tar 1.13.25-5
tcsh 6.12.00-7
termcap 20021106-2
terminfo 5.3_20030726-1
texinfo 4.2-4
textutils 2.0.21-1
unzip 5.50-5
which 1.5-2
zip 2.3-5
zlib 1.2.1-1
zsh 4.1.1-2
Use -h to see help about each section
[-- Attachment #3: Type: text/plain, Size: 218 bytes --]
--
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/
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Control-c not working in rxvt (for exiting jboss server)
2004-02-28 18:46 ` Control-c not working in rxvt (for exiting jboss server) Chuck Irvine
@ 2004-02-28 19:24 ` David Rothenberger
2004-02-28 21:20 ` Chuck Irvine
0 siblings, 1 reply; 11+ messages in thread
From: David Rothenberger @ 2004-02-28 19:24 UTC (permalink / raw)
To: Chuck Irvine; +Cc: cygwin
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/
^ permalink raw reply [flat|nested] 11+ messages in thread
* RE: Control-c not working in rxvt (for exiting jboss server)
2004-02-28 19:24 ` David Rothenberger
@ 2004-02-28 21:20 ` Chuck Irvine
2004-02-28 22:06 ` Igor Pechtchanski
` (2 more replies)
0 siblings, 3 replies; 11+ messages in thread
From: Chuck Irvine @ 2004-02-28 21:20 UTC (permalink / raw)
To: 'David Rothenberger'; +Cc: cygwin
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:daveroth@acm.org]
> Sent: Saturday, February 28, 2004 12:41 PM
> To: Chuck Irvine
> Cc: cygwin@cygwin.com
> 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/
^ permalink raw reply [flat|nested] 11+ messages in thread
* RE: Control-c not working in rxvt (for exiting jboss server)
2004-02-28 21:20 ` Chuck Irvine
@ 2004-02-28 22:06 ` Igor Pechtchanski
2004-02-28 23:25 ` David Rothenberger
2004-02-29 0:27 ` Larry Hall
2 siblings, 0 replies; 11+ messages in thread
From: Igor Pechtchanski @ 2004-02-28 22:06 UTC (permalink / raw)
To: Chuck Irvine; +Cc: cygwin
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:daveroth@acm.org]
> > Sent: Saturday, February 28, 2004 12:41 PM
> > To: Chuck Irvine
> > Cc: cygwin@cygwin.com
> > 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/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,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/
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Control-c not working in rxvt (for exiting jboss server)
2004-02-28 21:20 ` Chuck Irvine
2004-02-28 22:06 ` Igor Pechtchanski
@ 2004-02-28 23:25 ` David Rothenberger
2004-02-29 0:27 ` Larry Hall
2 siblings, 0 replies; 11+ messages in thread
From: David Rothenberger @ 2004-02-28 23:25 UTC (permalink / raw)
To: Chuck Irvine; +Cc: cygwin
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/
^ permalink raw reply [flat|nested] 11+ messages in thread
* RE: Control-c not working in rxvt (for exiting jboss server)
2004-02-28 21:20 ` Chuck Irvine
2004-02-28 22:06 ` Igor Pechtchanski
2004-02-28 23:25 ` David Rothenberger
@ 2004-02-29 0:27 ` Larry Hall
2004-02-29 0:35 ` Chuck Irvine
2 siblings, 1 reply; 11+ messages in thread
From: Larry Hall @ 2004-02-29 0:27 UTC (permalink / raw)
To: Chuck Irvine; +Cc: cygwin
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/
^ permalink raw reply [flat|nested] 11+ messages in thread
* RE: Control-c not working in rxvt (for exiting jboss server)
2004-02-29 0:27 ` Larry Hall
@ 2004-02-29 0:35 ` Chuck Irvine
2004-02-29 0:41 ` Christopher Faylor
2004-02-29 0:49 ` Larry Hall
0 siblings, 2 replies; 11+ messages in thread
From: Chuck Irvine @ 2004-02-29 0:35 UTC (permalink / raw)
To: 'Cygwin List'
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: cygwin@cygwin.com
> 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/
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Control-c not working in rxvt (for exiting jboss server)
2004-02-29 0:35 ` Chuck Irvine
@ 2004-02-29 0:41 ` Christopher Faylor
2004-02-29 0:49 ` Larry Hall
1 sibling, 0 replies; 11+ messages in thread
From: Christopher Faylor @ 2004-02-29 0:41 UTC (permalink / raw)
To: cygwin
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/
^ permalink raw reply [flat|nested] 11+ messages in thread
* RE: Control-c not working in rxvt (for exiting jboss server)
2004-02-29 0:35 ` Chuck Irvine
2004-02-29 0:41 ` Christopher Faylor
@ 2004-02-29 0:49 ` Larry Hall
1 sibling, 0 replies; 11+ messages in thread
From: Larry Hall @ 2004-02-29 0:49 UTC (permalink / raw)
To: Chuck Irvine, 'Cygwin List'
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: cygwin@cygwin.com
>> 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/
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2004-02-29 0:27 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-02-28 16:43 Control-c not working in rxvt Chuck Irvine
2004-02-28 18:33 ` Igor Pechtchanski
2004-02-28 18:46 ` Control-c not working in rxvt (for exiting jboss server) Chuck Irvine
2004-02-28 19:24 ` David Rothenberger
2004-02-28 21:20 ` Chuck Irvine
2004-02-28 22:06 ` Igor Pechtchanski
2004-02-28 23:25 ` David Rothenberger
2004-02-29 0:27 ` Larry Hall
2004-02-29 0:35 ` Chuck Irvine
2004-02-29 0:41 ` Christopher Faylor
2004-02-29 0:49 ` Larry Hall
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).