Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<20000809092454.4586.qmail@nwcst278.netaddress.usa.net>
Date:	9 Aug 00 03:24:54 MDT
From:	<norbert DOT bladt AT usa DOT net>
To:	cygwin <cygwin AT sources DOT redhat DOT com>
Subject:	Re: [Re: cygwin-1.1.4: problems with remote commands]
CC:	Ralf Fassel <ralf AT akutech DOT de>, norbert DOT bladt AT usa DOT net
X-Mailer:	USANET web-mailer (34FM0700.1.03)
Mime-Version:	1.0
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id JAA05569

Corinna Vinschen <vinschen AT cygnus DOT com> wrote:
> norbert DOT bladt AT usa DOT net wrote:
>> 
>> Ralf Fassel wrote:
[...]
>> > - using ssh, I am not able to see the output of remote commands in my
>> >   UNIX xterm.
>> >
>> >      % ssh nt-host ls
>> This works for me.
>> Either you
>>         - are using the ls from the Resource Kit or
>>         - have no home directory defined or it doesn't exist.
>> 
>> But the rest of your observation seems to be right.
>> In our environment we do start, stop and/or restart services
>> an this doesn't give any output on the UNIX side either.
>> But the rest of your observation seems to be right.
>> In our environment we do start, stop and/or restart services
>> an this doesn't give any output on the UNIX side either.

>You're right. I can reproduce that for telnet sessions.

>However, that is not what I'm expecting in ssh sessions:
The problem is not in an online session but in a remote command
given as a command line parameter on the client side, i.e.
	ssh -l user host /bin/ls -l
works fine, i.e. the output appears on the client side.
However,
	ssh -l user host net start clipsrv
doesn't give any output on the UNIX side (client)
if "host" is an NT system. Just the exit code
of "net start clipsrv" is returned. That's fine for me
but perhaps not for other users and other commands where you
want to interpret the output.
Forcing a pty (ssh option -t) does help with my version of ssh
and Corinna's version of sshd and cygwin 1.1.3, at least for the
"net start" commands. When this started to work, I don't know.
It didn't work in previous releases/ports of OpenSSH and cygwin.
But: I'm happy that this works now.

Cheers,

Norbert.


____________________________________________________________________
Get free email and a permanent address at http://www.netaddress.com/?N=1

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -