From: Gérard Henry (ghenry@cmi.univ-mrs.fr)
Date: Thu Sep 23 2004 - 10:22:01 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:
Roland.Merk
Raymond.Plassart
bryan pepin
remy.zandwijk
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
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:29:29 EDT