public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eli Barzilay <eli@barzilay.org>
To: cygwin@cygwin.com
Subject: ssh issues
Date: Thu, 05 May 2011 20:31:00 -0000	[thread overview]
Message-ID: <m3wri4opns.fsf@winooski.ccs.neu.edu> (raw)

Hopefully this is a FAQ in some place that I've missed...

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.)

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.

Any pointers?

-- 
          ((lambda (x) (x x)) (lambda (x) (x x)))          Eli Barzilay:
                    http://barzilay.org/                   Maze is Life!


--
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

             reply	other threads:[~2011-05-05 20:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-05 20:31 Eli Barzilay [this message]
2011-05-05 21:07 ` René Berber
2011-05-05 21:23   ` Charles Wilson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3wri4opns.fsf@winooski.ccs.neu.edu \
    --to=eli@barzilay.org \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).