X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: =?ISO-8859-1?Q?Ren=E9_Berber?= Subject: Re: ssh issues Date: Thu, 05 May 2011 16:07:17 -0500 Lines: 32 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.19) Gecko/20081209 Lightning/0.9 Thunderbird/2.0.0.19 Mnenhy/0.7.6.0 In-Reply-To: X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 5/5/2011 3:31 PM, Eli Barzilay wrote: > Hopefully this is a FAQ in some place that I've missed... Maybe not a FAQ but its a common complaint by people using VS; you might find more information on this list by searching over Visual Studio (which I don't use). > I have an XP machine set up for doing builds via ssh. This works fine > with one problem: when ssh is started normally as a service, there's > some obscure Visual Studio problem (it complains about some > misconfiguration). To solve it, I always kill sshd and start it from > a bash shell on the machine. It's tedious but not too much since the > machine is rarely rebooted. (I also have a monitor for this: it uses > ssh to log to the machine and then looks for sshd in the ps output.) >=20 > But now I'm trying to set up a Windows 7 build machine, and things get > more complicated in a way that I think is related to the above. The > first thing that fails (after I start sshd as myself, similarly to the > XP box) is running the vcvarsall.bat in the devstudio directory -- > that fails with a "Cannot determine the location of the VS Common > Tools folder", which I tracked down to uses of some `reg' command that > fail. The thing is that it works fine when running on a bash shell on > the machine, but fails through ssh. >=20 > Any pointers? Environment variables. When you login using ssh you get a different set than the ones your Windows login has, including a modified PATH. --=20 Ren=E9 Berber -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple