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: <20000809063835.13290.qmail@nwcst289.netaddress.usa.net>
Date:  9 Aug 00 00:38:35 MDT
From: <norbert DOT bladt AT usa DOT net>
To: Ralf Fassel <ralf AT akutech DOT de>
Subject: Re: cygwin-1.1.4: problems with remote commands
CC: cygwin AT sourceware DOT cygnus DOT com
X-Mailer: USANET web-mailer (34FM0700.1.03)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id LAA11368

Ralf Fassel wrote:
> 
> Hi all,
> experimenting with the ssh 2.1.1p4-2 daemon on Windows NT (SP6).  sshd
> runs fine for interactive logins, except:
> 
> - the `net use' command is not able to read a password.  First time it
>   prompts for the password, hangs a short while, then aborts with
>     'Systemfehler 86 aufgetreten.'  (System Error 86)
>   Following invocations abort immediately.  The password I typed is
>   used as commandline input for bash then.
> 
>   CYGWIN is set to `binmode ntsec tty'.  If I
>      export CYGWIN='binmode ntsec notty'
>      exec bash
>   behaviour is unchanged.  Haven't tried to set `notty' in the system
>   environment yet (would that help?)
> 
>   Same behaviour for sessions opened via telnetd and rshd.
> 
> - 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.
However, the exit codes work fine in these cases, i.e.
	0 means OK
	not 0 means error.
	in the case of "net start / stop"
	1 e.g.,ervice name does not exist
	2 e.g., service is already running (start) or doesn'^t run (stop)
This might be sufficient for your environment, too.
We'll use a combination of Samba and scp to do the file transfers.
If you use scp: remember it does a binary file transfer.
So, if you intend to use a textfile on NT which you prepared
on UNIX check whether LF must be converted to CRLF prior to sending.
And vice versa, of course.

Hope this helps,

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