From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18577 invoked by alias); 6 Jul 2005 02:59:13 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 18557 invoked by uid 22791); 6 Jul 2005 02:59:06 -0000 Received: from simon.cs.cornell.edu (HELO simon.cs.cornell.edu) (128.84.154.10) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Wed, 06 Jul 2005 02:59:06 +0000 Received: from sundial.cs.cornell.edu (sundial.cs.cornell.edu [128.84.96.115]) by simon.cs.cornell.edu (8.11.7-20031020/8.11.7/R-3.18) with ESMTP id j662x4u19850 for ; Tue, 5 Jul 2005 22:59:05 -0400 (EDT) Received: from tulare.cs.cornell.edu (IDENT:U2FsdGVkX198x869i9z/iibMH9Qv7D1wJbrWITPD6g0@tulare.cs.cornell.edu [128.84.97.197]) by sundial.cs.cornell.edu (8.11.7-20031020/8.11.7/M-3.22) with ESMTP id j662x4Q22441 for ; Tue, 5 Jul 2005 22:59:04 -0400 (EDT) Received: from tulare.cs.cornell.edu (IDENT:U2FsdGVkX1/gg1ZOV0yOZDPNYmfF7G6iUJiO4fpjZ+w@localhost.localdomain [127.0.0.1]) by tulare.cs.cornell.edu (8.12.11/8.11.7/L-1.5) with ESMTP id j662x4BY000876 for ; Tue, 5 Jul 2005 22:59:04 -0400 Received: (from eli@localhost) by tulare.cs.cornell.edu (8.12.11/8.12.11/Submit) id j662x3GD000872; Tue, 5 Jul 2005 22:59:03 -0400 From: Eli Barzilay MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17099.18679.819770.637448@tulare.cs.cornell.edu> Date: Wed, 06 Jul 2005 02:59:00 -0000 To: Cygwin List Subject: Re: ssh problems In-Reply-To: <6.2.1.2.0.20050705221013.08cdd6b0@pop.prospeed.net> References: <17099.10669.464228.125667@tulare.cs.cornell.edu> <6.2.1.2.0.20050705221013.08cdd6b0@pop.prospeed.net> X-SW-Source: 2005-07/txt/msg00169.txt.bz2 On Jul 5, Larry Hall wrote: > At 08:45 PM 7/5/2005, you wrote: > >(If this is not the right place for this, please direct me.) > > > >I have recently updated an old Windows setup, including a new cygwing > >installation. We use this machine for nightly builds, using a shell > >script that connects to multiple machines and runs the builds > >(DevStudio in the Windows case). With the new cygwin these builds > >stopped with a mysterious error -- about 5 hours later I know that the > >problem is with sshd and some permission problems. After a brief look > >at http://www.cygwin.com/cygwin-ug-net/ntsec.html, I tried moving my > >.ssh away so I have to type a password, and indeed the build works > >fine. > > > >So it looks like devstudio is doing something that requires some > >permissions that I don't get unless I physically type a password. Is > >there any way to solve this? I've been trying to play with things > >like ssh-host-config and stuff in the global CYGWIN, but nothing seem > >to be making it work. > > > You'll need to figure out what that "something" is that DevStudio is > doing. Is there any way to finding this? The most information I got was from the Event Viewer: Application popup: Microsoft Visual C++ Runtime Library : Runtime Error! Program: ...Microsoft Visual Studio .NET 2003\Common7\IDE\devenv.exe This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. > Sounds to me like you're trying to access a network drive which > requires authentication but that's just a WAG. But, if you think > that's it, see: > > Why don't my services work (or access network shares)? > This did sound like something similar, but it doesn't look like it's the problem. My script doesn't use any shares, and in case DevStudio does something funny I disconnected the only mapped share I had. Don't know what a "WAG" is, and the above faq entry didn't help... -- ((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay: http://www.barzilay.org/ Maze is Life! -- 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/