X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.3 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <ih3ntk$7aj$1@dough.gmane.org>
References: <AANLkTim5cbta847JdAoHpv565qqDMF=WEbZH6gFJ8Lih AT mail DOT gmail DOT com>	<4D34B5F0 DOT 1060103 AT bopp DOT net>	<AANLkTi=m0aJ+xo6Gcr_CYWtMcVJjc0SBxfubnuXeg3Br AT mail DOT gmail DOT com>	<4D34BD64 DOT 9050904 AT bopp DOT net>	<AANLkTi=9rNRhtx=dwQari9v+Rrsun9Yg1VwgTnZoNeLz AT mail DOT gmail DOT com>	<AANLkTikujecFG_j4-E1z8tD_9Zupy1TpW_cdFeJ52XTW AT mail DOT gmail DOT com>	<ih3ntk$7aj$1 AT dough DOT gmane DOT org>
Date: Wed, 19 Jan 2011 11:59:39 +1300
Message-ID: <AANLkTik5jFdKfG8Gza89zECW92Tu6tdV+xKUk_9=0SgH@mail.gmail.com>
Subject: Re: Invoking GUI programs over SSH
From: David Antliff <david DOT antliff AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Tue, Jan 18, 2011 at 22:52, Thorsten Kampe wrote:
> * David Antliff (Tue, 18 Jan 2011 13:13:22 +1300)
>> Along these lines, I was wondering if anyone knows how to run the
>> Cygwin SSH daemon manually, rather than as a service? On Linux one can
>> just run sshd from the command line, specifying an alternative port if
>> necessary. But in Cygwin I can't find sshd.exe or anything similarly
>> named.
>
> On Cygwin you do it the same way as you do it on Linux and the
> executable is in the same place as it is on Linux.

Thorsten, thank you. I had to adjust some folder permissions and grant
some special privileges (as described at the end of this page:
http://ist.uwaterloo.ca/~kscully/CygwinSSHD_W2K3.html), but once I did
that it seemed to work, at least running under a User rather than
Local System account.

Jeremy: thank you also - ProcessMonitor is very useful, and I'm using
it to compare the behaviour of the working (local) and non-working
(over SSH) instances. It's going to take me some time to sift though
them, but there are big differences:

Working: http://pastebin.com/W30xcT6P
Non-working: http://pastebin.com/Xt3an4Qs

The two logs diverge massively at line 12. The working instance
appears to start scanning the filesystem, whereas the non-working
instance starts going through registry keys. I'm not 100% convinced
I'm comparing oranges with oranges here, but I'm hoping there's a clue
somewhere.

I'll be spending some time trying to deduce what the problem might be,
but if anyone looks at those logs and can easily tell me, I'd really
appreciate it! :)

Thanks,

-- David.

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