X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <183c528b0711211317g332b6a40vdd15dd442dd694a8@mail.gmail.com>
Date: Wed, 21 Nov 2007 16:17:30 -0500
From: "Brian Mathis" <brian DOT mathis AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [Fwd: sshd display]
In-Reply-To: <E1Iuwe9-0003hZ-L3@owl.gateway.2wire.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <47447CDF DOT 5000604 AT cygwin DOT com> 	 <E1Iuwe9-0003hZ-L3 AT owl DOT gateway DOT 2wire DOT net>
X-IsSubscribed: yes
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

On Nov 21, 2007 3:58 PM, Robert Kiesling <kiesling AT earthlink DOT net> wrote:
> [ 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).


You're both missing the point.  Throwing in your two cents without
providing any help is just as bad, if not worse, than someone who's
asking a *possibly* off-topic question, which, since this involves
cygwin, is not likely.  If such a marginally off-topic message on this
incredibly high volume mailing list bothers you, there's a "delete"
button in your email client.


To help the OP:
An ssh connection typically does not create any sort of console window
on the system that is being connected to (this is the same on Linux or
Windows/Cygwin).  Depending on your needs, you may be able to emulate
something like this using 'screen'.

You can open screen in the local terminal (rxvt is recommended), and
start a screen session inside of it.  Then when you ssh in, you can
attach to that screen session using "screen -x" and both parties will
be able to see what's going on.  There's a little more to it than
that, and will probably need some experimentation, but that's
something that can get you started.

--
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/