Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	28 Jan 2004 13:49:55 -0000
To:	cygwin AT cygwin DOT com
Subject:	Issues with new cygwin1.dll and bash logouts
Encoding:	8bit
From:	"James Spinks" <agbrhrw502 AT sneakemail DOT com>
Message-ID:	<29502-14640@sneakemail.com>
Note-from-DJ:	This may be spam

Hi,

I have a .bash_profile script that calls the keychain program to ensure that ssh-agent is loaded and has all my usual keys loaded into it.

Since upgrading to the latest cygwin1.dll (and I've tried the lastest snapshot as well) everything works as before -- I can fire up the Cygwin bash shell, provide the password for my keys and access remote servers and do whatever I like.  The problem occurs when I try and exit the bash shell and it just sits there indefinitely until I kill the task.  When I re-launch Cygwin killing the previous bash session has taken out the ssh-agent process as well rather than it staying resident in the background as it used to.

It seems to me that as bash tries to exit it doesn't realise that the ssh-agent process is supposed to be detached and is trying to kill it as well.  Any suggestions as to how I can fix this behaviour, or any debugging type things I can do to ascertain the exact nature of the problem.

Ta,
James

--------------------------------------
Protect yourself from spam, 
use http://sneakemail.com

--
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/

- Raw text -