X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=em45v6hlIWv7f1ERZjnA2GIfVBw0TxE6gmTj77aBrAp
	MSqL+shhoM50sOgo8WAL/rRA1dcHssZ6+uYJpYk+SXlln37V4+sKX0fhHPAWYn2v
	u2HHLYITBIs5P5vsBsWItWeCKWhQRZcEm39dEZfEcwQMdwkxV+9OI4lKuWIf8qUQ
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=XvkSV2PpAJkyI3gdeubnXAvK3l4=; b=WO0suZRM9fsN67Ew3
	sVUUMnx8gYpItIMfejgBd/DFDptan1TXoZ/b9vQ2UDg3krwWu15hvF92Y4GWjL9J
	99SLoB6CgL3f50/tjAM6/ey+qu04eb5neidGjoQj34/ORxz5p7twyVvlzswFtW8n
	uxDL656tfC2eQuGhcsHSf3MVCA=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=1.9 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,FREEMAIL_REPLY,KAM_BODY_URIBL_PCCC,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2
X-HELO: mout.gmx.net
Message-ID: <54FE89C6.9060107@gmx.de>
Date: Tue, 10 Mar 2015 07:05:58 +0100
From: Herbert Stocker <hersto@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: possible to see windows created via sshd?
References: <7438.1425921069@franz.com> <105993732.20150309203517@yandex.ru>
In-Reply-To: <105993732.20150309203517@yandex.ru>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-UI-Out-Filterresults: notjunk:1;
X-IsSubscribed: yes

On 09.03.2015 18:35, Andrey Repin wrote:
> Greetings, Kevin Layer!
>
>> I'm running sshd on Windows (Server 2008 R2).  When I run Windows
>> programs via ssh the windows are not visible.  I realize this is a
>> long shot, but is there any fix or workaround or hack to this?
>
> This is OS architectural change coming from Vista.
>
>> We run sshd under the cyg_server domain account.
>
> Doesn't matter the user, services are running in a separate desktop session.
> Only way to work around this is to start services from already logged in
> user session, then windows will be created in it and will be visible.

i have another approach. i start a screen session from the logged in
user session and when i connect to my windows machine via ssh, i connect
to this screen session and start my windows programs there. screen is a
tool that comes with Cygwin.

screen also has another advance: if your ssh connection drops, or you
have to log out, your Cygwin command line tools and Windows programs
remain running.

BTW, after starting a screen session you can disconnect from it and
close the mintty window or DOS box you used for that. So there is no
such window remaining on your desktop.


best regards,

Herbert


> But I feel that you've had different question in mind altogether.
>
>
> --
> WBR,
> Andrey Repin (anrdaemon@yandex.ru) 09.03.2015, <20:32>
>
> Sorry for my terrible english...
>
>
> --
> 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
>


-- 
+49 176 6289 1952
+49 151 726 46412

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

