Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: Thu, 20 Feb 2003 16:35:26 +0000 Message-ID: <767-Thu20Feb2003163526+0000-starksb@ebi.ac.uk> From: David Starks-Browning MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Jim Kleckner Cc: cygwin AT cygwin DOT com Subject: Re: rxvt dialog at shutdown suggests failure to exit due to ssh-agent? In-Reply-To: <3E55007F.3010500@kleckner.net> References: <3E53C564 DOT 4070007 AT kleckner DOT net> <5420-Thu20Feb2003113550+0000-starksb AT ebi DOT ac DOT uk> <3E55007F DOT 3010500 AT kleckner DOT net> On Thursday 20 Feb 03, Jim Kleckner writes: > Thank you for the suggestion. > > David Starks-Browning wrote: > > > On Wednesday 19 Feb 03, Jim Kleckner writes: > [snip] > > If *all* shells source that line, then you have the problem that the > > first one to exit will kill ssh-agent, and maybe you don't want that. > > You could put something a bit more sophisticated in your .bash_profile > > (or whatever) to identify a "master" shell, depending on your > > requirements. > > Unfortunately, this is exactly what keychain is for - > to start the agent in one shell and then share access > from many shells. I start up and shut down many rxvt/bash > shells during the day without having to provide my > passphrase. Stopping the agent with keychain is easy by > just typing "keychain -k". I forget to do that just > about every time. Your exit trap function could be something that checks to see if it's the last rxvt window remaining, and if so, runs "keychain -k". (I agree, this is a workaround. It would be nicer if ssh-agent would die quickly and quietly at Windows logout or shutdown. I don't know if that's possible.) Regards, David -- 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/