Prev: old laptop rebirth with 32 meg ram with wireless
Next: Is google sabotaging browsers?
From: Todd on 5 Mar 2010 23:29
Hi All,

Guest: Fedora Core 12 (FC12)
Host: CentOS 5.4 (Red Hat Enterprise clone)

I have been playing with "ssh -X". In my test, I fire up Firefox
on my FC12 guest.

Problem: after I exit firefox, my calling line from my host does not
terminate. I have to <ctrl><C> to get my command prompt back.
(The "Killed by signal 2" below is me pressing <ctrl><C>.)

$ ssh -X 192.168.255.185 /usr/bin/firefox -no-remote
todd(a)192.168.255.185's password:
Killed by signal 2.

What am I missing?

Many thanks,
-T
From: General Schvantzkoph on 6 Mar 2010 09:07
On Fri, 05 Mar 2010 20:29:23 -0800, Todd wrote:

> Hi All,
>
> Guest: Fedora Core 12 (FC12)
> Host: CentOS 5.4 (Red Hat Enterprise clone)
>
> I have been playing with "ssh -X". In my test, I fire up Firefox on my
> FC12 guest.
>
> Problem: after I exit firefox, my calling line from my host does not
> terminate. I have to <ctrl><C> to get my command prompt back. (The
> "Killed by signal 2" below is me pressing <ctrl><C>.)
>
> $ ssh -X 192.168.255.185 /usr/bin/firefox -no-remote
> todd(a)192.168.255.185's password:
> Killed by signal 2.
>
> What am I missing?
>
> Many thanks,
> -T

Just type
exit

From: Todd on 6 Mar 2010 17:26
On 03/06/2010 06:07 AM, General Schvantzkoph wrote:
> On Fri, 05 Mar 2010 20:29:23 -0800, Todd wrote:
>
>> Hi All,
>>
>> Guest: Fedora Core 12 (FC12)
>> Host: CentOS 5.4 (Red Hat Enterprise clone)
>>
>> I have been playing with "ssh -X". In my test, I fire up Firefox on my
>> FC12 guest.
>>
>> Problem: after I exit firefox, my calling line from my host does not
>> terminate. I have to<ctrl><C> to get my command prompt back. (The
>> "Killed by signal 2" below is me pressing<ctrl><C>.)
>>
>> $ ssh -X 192.168.255.185 /usr/bin/firefox -no-remote
>> todd(a)192.168.255.185's password:
>> Killed by signal 2.
>>
>> What am I missing?
>>
>> Many thanks,
>> -T
>
> Just type
> exit

Tried exit, quit, logoff, bad words. No joy. The only thing
I found that worked is <ctrl><C>.

Is there something in the run string I could do that tells
it to quit when firefox quits?

Many thanks,
-T

From: Dave U. Random on 7 Mar 2010 11:02
"T" =3D=3D Todd <t...(a)invalid.com>:
T> I have been playing with "ssh -X". In my test, I fire up Firefox on m=
y
T> FC12 guest.
T> Problem: after I exit firefox, my calling line from my host does not
T> terminate.
T> Tried exit, quit, logoff, bad words. No joy. The only thing
T> I found that worked is <ctrl><C>.

Read the man page that came with the program, ie. ssh(1).=20

Pay special attention to the 'Escape Characters' section...

From: Todd on 7 Mar 2010 18:20
On 03/07/2010 08:02 AM, Dave U. Random wrote:
> "T" =3D=3D Todd<t...(a)invalid.com>:
> T> I have been playing with "ssh -X". In my test, I fire up Firefox on m=
> y
> T> FC12 guest.
> T> Problem: after I exit firefox, my calling line from my host does not
> T> terminate.
> T> Tried exit, quit, logoff, bad words. No joy. The only thing
> T> I found that worked is<ctrl><C>.
>
> Read the man page that came with the program, ie. ssh(1).=20
>
> Pay special attention to the 'Escape Characters' section...
>

Hi Dave,

No joy. What am I missing?

Maybe because I am using "-X", I do not have a
"pseudo-terminal"?

-T

-e escape_char
Sets the escape character for sessions with a pty (default: �~�).
The escape character is only recognized at the beginning of a
line. The escape character followed by a dot (�.�) closes the
connection; followed by control-Z suspends the connection; and
followed by itself sends the escape character once. Setting the
character to �none� disables any escapes and makes the session
fully transparent.

If a pseudo-terminal has been allocated (normal login session),
the user may use the escape characters noted below.



$ ssh -X 192.168.255.185 /usr/bin/firefox --no-remote
todd(a)192.168.255.185's password:
~.
~.exit
~20
~\20
..
/?
help
exit
~exit
..exit
~~
~?
Killed by signal 2. <<---<ctrl><C>
 |  Next  |  Last
Pages: 1 2 3 4
Prev: old laptop rebirth with 32 meg ram with wireless
Next: Is google sabotaging browsers?