X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Subject: Re: [Fwd: sshd display]
In-Reply-To: <47447CDF.5000604@cygwin.com>
To: cygwin AT cygwin DOT com
Date: Wed, 21 Nov 2007 15:58:09 -0500 (EST)
X-Mailer: ELM [version 2.4ME+ PL124 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <E1Iuwe9-0003hZ-L3@owl.gateway.2wire.net>
From: Robert Kiesling <kiesling AT earthlink DOT net>
X-ELNK-Trace: 0b901cbc512a9d8594f5150ab1c16ac01a238acc8405a5b00dceaf609efd6e9ed5fc5e2424f235b9350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

[ Charset UTF-8 unsupported, converting... ]
> On 11/21/2007, Uber Zooka wrote:
> > Because he's trying to go from a linux machine to a machine running 
> > Cygwin.... 
> 
> I think you're missing my point.  If there's an answer to this question
> in the Linux->Linux case (or on any other UNIXy platforms that don't include
> Cygwin) then that same approach should work on Cygwin.  If it doesn't, then
> that's a Cygwin issue and on-topic.  If it does work, then that's the answer
> to the question and Cygwin has no bearing, thus the original inquiry is
> off-topic.
> 
> > He's trying to run an app on a windows machine and wants to know 
> > how to make the console on the windows machine stay there.
> 
> Since 'ssh' is a client program on the client machine that's logging in
> remotely to the server machine, there's nothing visible on the server.
> Output goes to the client terminal.  There's no visible mechanism on the
> server for this output to "stay" on.  There may be other ways to achieve
> something that would be a reasonable alternative in this case but that
> would presuppose that we understand what actual problem the OP was trying
> to solve.  That's why I suggested he provide more info if he has a Cygwin-
> specific issue.

An off-topic answer would be xon(1).

-- 
Ctalk Home Page: http://ctalk-lang.sourceforge.net


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/