Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <3969C562.CBB5AAD@cygnus.com>
Date: Mon, 10 Jul 2000 14:45:22 +0200
From: Corinna Vinschen <vinschen@cygnus.com>
Reply-To: cygwin <cygwin@sourceware.cygnus.com>
MIME-Version: 1.0
To: norbert.bladt@usa.net
CC: cygwin@sourceware.cygnus.com
Subject: Re: Openssh port to cygwin
References: <20000710113445.18876.qmail@nwcst313.netaddress.usa.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

norbert.bladt@usa.net wrote:
> 
> Hello everyone !
> 
> Openssh on NT works very well, unless you are trying to
> use /winnt/system32/cmd instead of /bin/sh or
> unless you use real NT commands from the sh.
> 
> In this case, no input / output redirection is possible,
> neither on UNIX nor - once logged in - on NT.
> Using "cygwin-enabled" GNU commands works fine, though.
> 
> Now my questions are:
> Is this the intended behaviour ?
> If not what can be the reason or - with other words - do
> just I see this behaviour or is it the same for everybody else ?
> 
> We really want to execute NT commands like "net use" or
> "net stop snmp", etc. from remote UNIX or NT host via ssh.
> Is this a bad idea and if yes, why ?
> Are there other WORKING solutions for that which are secure ?

I'm using nt commands via ssh without problems as far as they
are not GUI commands. CLI tools like `net' are working _mostly_
fine. Some commands like `sc' sometimes have dubious problems
with their output.

Try setting the environment variable CYGWIN so that it contains
`tty'. This might help.

Corinna

-- 
Corinna Vinschen
Cygwin Developer
Cygnus Solutions, a Red Hat company

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com