This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
Re: how to get rid of running xterm after a remote x application start ?
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: cygwin-xfree at cygwin dot com
- Date: Thu, 19 Aug 2004 15:16:27 -0400
- Subject: Re: how to get rid of running xterm after a remote x application start ?
- References: <20040819135537.41248.qmail@web40110.mail.yahoo.com> <4124E405.3030509@scytek.de>
- Reply-to: cygwin-xfree at cygwin dot com
- Reply-to: cygwin-xfree at cygwin dot com
On Thu, Aug 19, 2004 at 10:31:49AM -0700, Volker Quetschke wrote:
>>apology if this is not the right place to ask my question.
>
>Well, strictly speaking it is a common *nix question, but as it points
>out a problem I usually have I'll give a partial answer.
>
>After looging in to your server try:
>
>$ nohup xclock &
>
>(Use your application instead of xclock ;) ) You will see the
>application coming up and you can try to exit your ssh shell now.
>
>This works as desired, but my problem is that exiting ssh with "exit"
>never finishes. I have to kill the windows rxvt window. (I usually
>use rxvt, I don't know if it would work with ssh from bash started in
>cmd.exe)
Try using 'setsid xclock' instead.