This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: [Fwd: sshd display]
- From: Robert Kiesling <kiesling at earthlink dot net>
- To: cygwin at cygwin dot com
- Date: Wed, 21 Nov 2007 15:58:09 -0500 (EST)
- Subject: Re: [Fwd: sshd display]
[ 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/