Re: bash, background java VMs and ctrl-C

Re: bash, background java VMs and ctrl-C

[Brian P Kasper]

Jeff --

Check the value of the CYGWIN environment variable
for you and your coworker who isn't having the problem.
Does your coworker have 'tty' in the variable?  Do you
not have it?

I had a problem with ^C killing ssh sessions over which
I was tunnelling X Windows packets.  I was able to work
around the problem by adding 'tty' to my CYGWIN variable.

-Brian Kasper
 The Aerospace Corporation
 kasper@aero.org


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: bash, background java VMs and ctrl-C

[Jeff Meredith]

That does the trick! Life is sweet (again). Thank you very much.


Jeff meredith
mer@edgility.com


-----Original Message-----
From: Brian P Kasper [mailto:Brian.P.Kasper@aero.org] 
Sent: Tuesday, February 26, 2002 2:10 PM
To: cygwin@cygwin.com
Cc: jmeredith@edgility.com
Subject: Re: bash, background java VMs and ctrl-C

Jeff --

Check the value of the CYGWIN environment variable
for you and your coworker who isn't having the problem.
Does your coworker have 'tty' in the variable?  Do you
not have it?

I had a problem with ^C killing ssh sessions over which
I was tunnelling X Windows packets.  I was able to work
around the problem by adding 'tty' to my CYGWIN variable.

-Brian Kasper
 The Aerospace Corporation
 kasper@aero.org


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

bash, background java VMs and ctrl-C

[Jeff Meredith]

I have a difficult time with the following bash (or maybe cygwin.dll)
behavior:
	bash-2.05a$> java com.edgility.<blah>.ClassName &
	bash-2.05a$> tail -f mylogfile
	...
	ctrl-C

as soon as I hit ctrl-C the java VM exits.

In the bash reference manual it talks about background processes being
in different process groups and not propagating a SIGINT to those
processes.

I read through every option available to stty and tried various ones
that sounded related with no effect. I have also tried starting the VM
with: (trap "" 1 2 3; java com.edgility.<blah>.Classname &) also with no
effect.

Further, I read a lot in the mail archive for this group about bash vs.
cmd and the difference between ctrl-C and ctrl-break and how cygwin.dll
handles interrupts. It looks like a change went into 1.3.7 controlling
how signals are propagated, but I wasn't clear on exactly what effect
the change had. I was running 1.3.6 and upgraded to 1.3.9 and the
behavior is exactly the same in both cases for me. What is absolutely
baffling is that a co-worker is also running 1.3.9 and the same version
of bash and he does not see this behavior.

All of this leaves me wondering, 1. what is supposed to happen to
background processes in bash when one types the interrupt character? 2.
is there some configuration option that affects this?

Any insights (penetrating or otherwise) would be appreciated,
jeff meredith (jmeredith@edgility.com)


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/