X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Date: Tue, 5 May 2009 07:01:54 -0400 From: To: Subject: Re: Trouble with ssh-agent (maybe opening socket?) Message-ID: <20090505110154.GB28884@certicom.com> Reply-To: avadekar AT certicom DOT com References: <20090505080339 DOT GA30961 AT mail DOT christiananton DOT de> <20090505091545 DOT GU21324 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20090505091545.GU21324@calimero.vinschen.de> User-Agent: Mutt/1.4.2.3i X-CRXEFW-Info: Please contact Ceryx for more information X-CRXEFW-Virus: Clean X-CRXEFW-From: avadekar AT certicom DOT com X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 I occasionally see something similar. I can only describe it has managing to log in and get ssh-add started by my first shell before windows has sucessfully started something related to the network stack. In this case, ssh (and maybe any other cygwin socket programs) simply wont work. I have to either log out or maybe even reboot. strace shows a socket operation blocking. As long as I wait for the login process to finish (HD goes idle after login), it never happens. Its annoying because I can usually log in ssh out and read my mail then be done before windows even finished logging in. This behaviour started last fall after a windows update, if I recall correctly. On Tue, May 05, 2009 at 06:15:45AM -0400, Corinna Vinschen wrote: > On May 5 10:03, Christian Anton wrote: > > Now i have absolutely no idea what the problem is, i only see that ssh-agent > > starts to get crazy eating all cpu time it can get when ssh-add is trying to > > access its socket. > > I can't reproduce this problem. > > > Do you have any idea how to debug this problem? It is really annoying to > > work with ssh and entering the private key's password on every new > > connection... > > Maybe a BLODA problem? > See http://cygwin.com/1.7/faq/faq.using.html#faq.using.bloda > > > Corinna > > -- > Corinna Vinschen Please, send mails regarding Cygwin to > Cygwin Project Co-Leader cygwin AT cygwin DOT com > Red Hat > > -- > 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/ -- 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/