RE: [cobalt-developers] Control + S lockup.

["Hosting Sales" <hosting@xxxxxxxxxxx>]

> -----Original Message-----
> From: cobalt-developers-admin@xxxxxxxxxxxxxxx
[mailto:cobalt-developers-
> admin@xxxxxxxxxxxxxxx] On Behalf Of Matthew Nuzum
> Sent: Friday, November 23, 2001 9:46 PM
> To: cobalt-developers@xxxxxxxxxxxxxxx
> Subject: [cobalt-developers] Control + S lockup.
> 
> OK, this has been mildly annoying for some time, but I've finally had
> the last straw.  So now I'm going to ask for help.
> 
> First, here's the setup:
> Raq4i
> SSH
> Putty as the client.
> 
> The problem is repeatable.
> 
> Whenever I use pico, pressing Ctrl+s causes the SSH session to stop
> responding.  No subsequent key sequence that I can think of will fix
> this.  I do not have this problem on my RH7.1 server, so I'm not sure
> what the cause is.
> 
> Here's the details:  I usually run emacs as my main programming
> environment.  To save a file in emacs, you Ctrl+x, Ctrl+s.  I like to
do
> this whenever I've made a major change that would make me cry if I
lose
> it.
> 
> Well, when I'm operating as root, my emacs preferences aren't
available,
> so I use pico.  The only problem is, pressing Ctrl+s in pico causes
the
> very thing you don't want to happen.  Instead of saving your work, it
> freezes, causing you to lose your work.
> 
> Because this doesn't happen on my other server, I have to wonder what
> causes it.  Could it be my firewall?  If so, why can I press Ctrl+s in
> emacs?  Maybe it's the terminal settings in the Raq?
> 
> Any suggestions?
> 
> Matthew Nuzum
> 5`//337-31337
> followers.net


You are probably using a terminal emulation often called "software
handshaking".  Control-s [XOF] sent from your client to the server tells
it to stop sending data.  Similarly, control-q [XON] tells the server to
resume.  To test whether this is your problem, after you "lock up"
following transmission of control-s, press control-q to see if stuff
unlocks.  If so, it still doesn't help you since the comms protocol eats
the XON/XOF characters and they are not delivered to the app.  But at
least you can continue the session.

So, you will need to check your terminal emulation key mappings.  I'm
hardly an expert in this field, but see what the setup is for emacs and
for pico when you run as root.  You should find some differences as to
how these keys are handled by the server.  Perhaps someone who knows
more out the specifics of keyboard mappings might jump in with
specifics.

Jack