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: <6.0.1.1.0.20040402092220.02100e98@mail.earthlink.net> X-Sender: cmorlier AT mail DOT earthlink DOT net Date: Fri, 02 Apr 2004 09:33:58 -0600 To: cygwin AT cygwin DOT com From: "Christopher G. Morlier" Subject: Re: patch for keychain In-Reply-To: <406CEF3E.9040002@pobox.com> References: <406CEF3E DOT 9040002 AT pobox DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed At 10:42 PM 4/1/2004, Bill Smargiassi wrote: >I noticed this with a recent Cygwin install. $HOME was set to my user dir >in C:\Documents and Settings. Several of the tests on $keydir and $pidf >were not quoted and the spaces in $HOME were causing "too many arguments" >errors. As a result, the agent info was not stored properly and closing >the shell that started keychain would result in a hung cmd.exe or >rxvt.exe. So far things are working as they should after these changes to >quote variables in 3 tests and a "." sourcing of $pidf. ...snip... I have observed the behavior you describe, with cmd.exe locking up when I logout of cygwin, and only in the terminal that started keychain. However, I do not have any spaces in my $HOME. I applied the patch, but I am still encountering this problem. Any other suggestions as to what would cause this problem? I just updated all my Cygwin packages this morning, and run Windows XP Home. Thanks, Chris -- 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/