[SUMMARY]: can't send break in tip

From: Gérard Henry <ghenry_at_cmi.univ-mrs.fr>
Date: Thu Sep 23 2004 - 10:23:48 EDT
many thanks for fast replies from a lot of people.
The answer seems simple:
for example, h. kreft said:
"Because ~# is interpreted by the SSH you used to connect to said blade
100. If you want to send tip the sequence '~#' you may either change the
escape character of your ssh client by specifying the -e parameter"

i forgot to say i'm using ssh!
another suggestion was to do:
"Try ~~# after a newline. You have to escape ~ so tip can see ~ as its
escape character."
it can't works for me, i don't know why.

Finally, i just did:
~s to change value of escape character, here i use $, and then type $$#
and it works fine.

thanks to:
bryan pepin
rene occelli
chris pinnock
helmut kreft

> i've a machine administered with a serial cable beetween port A and port 
> B of a sun blade 100.
> On sun blade 100, in a terminal, i use tip -9600 /dev/cua/b to connect.
> I want to send a break to the remote machine, with ~#, but it don't work:
> ~#
> The following connections are open:
>   #0 client-session (t4 r0 i1/0 o16/0 fd 6/7)
> and if i do:
> ~?
> Supported escape sequences:
> ~.  - terminate connection
> ~^Z - suspend ssh
> ~#  - list forwarded connections
> ~&  - background ssh (when waiting for connections to terminate)
> ~?  - this message
> ~~  - send the escape character by typing it twice
> (Note that escapes are only recognized immediately after newline.)
> i see that ~# is not for send a break, why?
sunmanagers mailing list
Received on Thu Sep 23 10:23:40 2004

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:37 EST