Re: How to prevent application info getting sent back to SSH client

From: Garry Shum (netname@hotmail.com)
Date: 09/25/02 

From: Garry Shum <netname@hotmail.com>
Date: Tue, 24 Sep 2002 20:37:18 -0400

I've tried all sorts of Posix redirection for NT/2K, and no go. The
only thing that worked was using a bash shell under NT/2K. Then it
worked fine and is currently what I'm using.

On Sat, 21 Sep 2002 13:35:01 GMT, "Nico Kadel-Garcia"
<nkadel@bellatlantic.net> wrote:

>
>"Garry Shum" <netname@hotmail.com> wrote in message
>news:rgunou8mda84l12j32d5g6dhvaftvi9938@4ax.com...
>> I figured it had something to do with redirection /dev/null. Tried
>> using the -n option but didn't do a thing. It works with...
>>
>> ssh -l administrator ntmachine "c:/opera/opera.exe > /dev/null"
>>
>> ...works great. The only drawback is that the SSH client session
>> doesn't immediately end after the command is sent. The shell running
>> the command on the SSH server machine has to complete before the SSH
>> client session will exit.
>
>Oy. I have *no* idea how to do output redirection in NT, but recent versions
>of OpenSSH don't close the session until stdout, stderr, and stdin are
>closed off (as they are called in the UNIX world). That's why I had the
>"2>/dev/null" for UNIX, to redirect stderr, and "</dev/null", to redirect
>stdin.
>
>For NT, I assume you need to do something similar, at least to stdin if not
>to some form of stderr.
>

Quantcast