[Date Prev] [Date Index] [Date Next] [Thread Prev] [Thread Index] [Thread Next]
Michael Redinger Michael.Redinger@uibk.ac.at
Thu, 27 Apr 2006 06:20:57 -0700 (PDT)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I am having problems sending a break signal to Opengear console servers: When I connect to the opengear port directly using ssh, I can send the break signal using ~~b. I tried the same with conserver: The connection is made using ssh, and I set break to ~b. However, a real "~b" (the string, not a break signal) is sent then. I also tried ~~b and even ~~~b. Same result. Break signals work fine for me using eg. Cyclades consoles. I configured ~break as the break string, works fine here. So I do not think "~" is interpreted before it comes to conserver, right? I found two documents that seem related, but could not find anything there that helps me understand this ... https://www.conserver.com/pipermail/users/2006-February/msg00010.html http://www.conserver.com/consoles/BREAK-off/breakinfo.html Thanks, Michael - -- Michael Redinger Zentraler Informatikdienst (Central IT Services) Universitaet Innsbruck Technikerstrasse 13 Tel.: ++43 512 507 2335 6020 Innsbruck Fax.: ++43 512 507 2944 Austria Mail: Michael.Redinger@uibk.ac.at BB98 D2FE 0F2C 2658 3780 3CB1 0FD7 A9D9 65C2 C11D http://homepage.uibk.ac.at/~c102mr/mred-pubkey.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFEUMUrD9ep2WXCwR0RAj72AKDy/QETCmbMU9xNrEMxFfxLuqYXxgCdGhNo 6w3tHTHJjZEJ8MsWEqbdY+U= =EmJl -----END PGP SIGNATURE-----