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 Message-ID: <3E55007F.3010500@kleckner.net> Date: Thu, 20 Feb 2003 08:21:19 -0800 From: Jim Kleckner User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3 X-Accept-Language: en-us MIME-Version: 1.0 To: David Starks-Browning CC: cygwin AT cygwin DOT com Subject: Re: rxvt dialog at shutdown suggests failure to exit due to ssh-agent? References: <3E53C564 DOT 4070007 AT kleckner DOT net> <5420-Thu20Feb2003113550+0000-starksb AT ebi DOT ac DOT uk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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. This is not a big problem. I just thought someone might know how to "strongly detach" the process while at the same time allowing stdin interaction for the passphrase. Jim -- 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/