Tjyylli

Is "history" a male-biased word ("his+story")?

What is the dot in “1.2.4."

Is it ok to include an epilogue dedicated to colleagues who passed away in the end of the manuscript?

How is the Swiss post e-voting system supposed to work, and how was it wrong?

Should we release the security issues we found in our product as CVE or we can just update those on weekly release notes?

Good allowance savings plan?

The three point beverage

Deleting missing values from a dataset

Am I not good enough for you?

What has been your most complicated TikZ drawing?

Decoding assembly instructions in a Game Boy disassembler

Unreachable code, but reachable with exception

Playing ONE triplet (not three)

Running a subshell from the middle of the current command

Co-worker team leader wants to inject the crap software product of his friends into our development. What should I say to our common boss?

Is King K. Rool's down throw to up-special a true combo?

Is a lawful good "antagonist" effective?

Why must traveling waves have the same amplitude to form a standing wave?

Is it true that real estate prices mainly go up?

What Happens when Passenger Refuses to Fly Boeing 737 Max?

Can the druid cantrip Thorn Whip really defeat a water weird this easily?

Humans have energy, but not water. What happens?

What wound would be of little consequence to a biped but terrible for a quadruped?

What does it mean when multiple 々 marks follow a 、?

Can you disable the Ctrl-S (XOFF) keystroke in Putty?

Pressing “Ctrl + S” by mistake while using VimHow do I disable the PuTTY bell via a command line parameter?Can you set up PuTTY to SSH into machine through another machine (through an SSH tunnel)How can i disable Pageant in Putty in command line?How can I configure putty to retain the feed from nano on the screen after exiting?Putty: limit to where you send your keysstty: standard input: Invalid argument error when scping filesCtrl + arrow keys for tmux not working in PuTTYPuTTY: disable copy-paste on mouse selectionPuTTY: send over serial connection without ctrl+JCan ping ubuntu server, but not connect with putty

39

17

I do a lot of ssh-ing, and periodically I hit Ctrl+S, which naturally sends an XOFF, and causes all kinds of problems (not to mention it takes a while for me to figure out what happened, then another while to remember that I need to press Ctrl+Q to recover.

I would much rather instruct Putty to never ever let me type XOFF.

Any ideas?

ssh terminal putty

share|improve this question

edited Jan 13 '15 at 14:45

Community♦

1

asked Mar 27 '10 at 20:55

SethSeth

6872814

• 
  
  
  

  
  5
  

  
  
  
  
  
  

  
  
  +1 for pointing out that recovery is possible with Ctrl+Q. Helped me a lot!
  
  – Demento
  Apr 21 '11 at 17:49
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  +1 for actually asking how to disable this behavior because it's completely antiquated and useless for my purposes. Everybody on the web has the CTRL+q trick documented, but nobody has documented how to unbind the keys altogether.
  
  – andrew
  Mar 11 '12 at 8:47
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  keep in mind that ctrl+q will restore the cached flow. That means, if you press ctrl+s and then go crazy pressing ctrl+c or anything else, when you press ctrl+q all that you pressed before will be played out.
  
  – gcb
  Apr 17 '13 at 19:35
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  What is the effect of an XOFF?
  
  – Snowcrash
  Jul 18 '18 at 10:54
  

  
  
  
  

add a comment | 

39

17

I do a lot of ssh-ing, and periodically I hit Ctrl+S, which naturally sends an XOFF, and causes all kinds of problems (not to mention it takes a while for me to figure out what happened, then another while to remember that I need to press Ctrl+Q to recover.

I would much rather instruct Putty to never ever let me type XOFF.

Any ideas?

ssh terminal putty

share|improve this question

edited Jan 13 '15 at 14:45

Community♦

1

asked Mar 27 '10 at 20:55

SethSeth

6872814

• 
  
  
  

  
  5
  

  
  
  
  
  
  

  
  
  +1 for pointing out that recovery is possible with Ctrl+Q. Helped me a lot!
  
  – Demento
  Apr 21 '11 at 17:49
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  +1 for actually asking how to disable this behavior because it's completely antiquated and useless for my purposes. Everybody on the web has the CTRL+q trick documented, but nobody has documented how to unbind the keys altogether.
  
  – andrew
  Mar 11 '12 at 8:47
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  keep in mind that ctrl+q will restore the cached flow. That means, if you press ctrl+s and then go crazy pressing ctrl+c or anything else, when you press ctrl+q all that you pressed before will be played out.
  
  – gcb
  Apr 17 '13 at 19:35
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  What is the effect of an XOFF?
  
  – Snowcrash
  Jul 18 '18 at 10:54
  

  
  
  
  

add a comment | 

I do a lot of ssh-ing, and periodically I hit Ctrl+S, which naturally sends an XOFF, and causes all kinds of problems (not to mention it takes a while for me to figure out what happened, then another while to remember that I need to press Ctrl+Q to recover.

I would much rather instruct Putty to never ever let me type XOFF.

Any ideas?

ssh terminal putty

share|improve this question

edited Jan 13 '15 at 14:45

Community♦

1

asked Mar 27 '10 at 20:55

SethSeth

6872814

share|improve this question

edited Jan 13 '15 at 14:45

Community♦

1

asked Mar 27 '10 at 20:55

SethSeth

6872814

share|improve this question

edited Jan 13 '15 at 14:45

Community♦

1

asked Mar 27 '10 at 20:55

SethSeth

6872814

edited Jan 13 '15 at 14:45

Community♦

1

edited Jan 13 '15 at 14:45

Community♦

1

asked Mar 27 '10 at 20:55

SethSeth

6872814

asked Mar 27 '10 at 20:55

SethSeth

6872814

6 Answers
6

active

oldest

votes

33

Don't know about Putty, but you can use:

stty -ixon

on remote host, to disable START/STOP signals.

share|improve this answer

edited Feb 22 '11 at 11:42

answered Mar 27 '10 at 22:10

BartoszBartosz

44645

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks - any idea if or how this affects the console? Would it alter the behavior of shell programs? (The only thing I know about XON/XOFF is that it's used for serial flow control). Sounds like a good setting for .bash_profile.
  
  – Seth
  Mar 29 '10 at 16:57
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  That should be stty -ixon.
  
  – Oddthinking
  Feb 16 '11 at 1:44
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Sorry. Updated my post to fix the typo.
  
  – Bartosz
  Feb 22 '11 at 11:43
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  As I just commented to BlakBat on his answer, that makes ^S not send an XOFF, but it now puts me into i-search mode. Is there a way I can get bash (or PuTTY) just to discard any ^S? Even better would be if it could beep and/or flash at me ;o)
  
  – Owen Blacker
  Feb 14 '12 at 15:06
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  I've added stty -ixon to my profile scripts. I've read about 100 articles on how when you press CTRL+s by accident, all you have to do is CTRL+q to resume again...but I don't want my shell to intercept CTRL+s/q at all since I use them with vim quite a bit. Thank you so much for providing an answer nobody else seems to even consider.
  
  – andrew
  Mar 11 '12 at 8:46
  

  
  
  
  

add a comment | 

28

The PuTTY solution:

1. before creating the session go navigate to Connection->SSH->TTY in the list.


2. in the "Mode" dropdown box, select IXON (nb: as of version 0.60, this list is not alphabetically ordered)


3. put "0" (zero) as the value of IXON.

Works as a charm, even if you open up a "GNU screen" on top of it, SSH to another host, or "su" to another user

If you're using GNU Bash, ctrl-S should allow you now to do a forward-search-history (aka: i-search)

You can see the difference in the output of "stty -a | grep -o ".ixon":
With putty configured it prints "-ixon", without " ixon"

share|improve this answer

edited Jan 11 '12 at 14:29

answered Jan 10 '12 at 15:11

BlakBatBlakBat

7351819

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Ok, that makes ^S not send an XOFF, but it now puts me into i-search mode. Is there a way I can get PuTTY (or bash) just to discard any ^S? Even better would be if it could beep and/or flash at me ;o)
  
  – Owen Blacker
  Feb 14 '12 at 15:05
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  To deactivate an action, you can bind ^S to nothing via bind '"C-s"'. This makes my PuTTY blink because the action is not mapped.
  
  – BlakBat
  Apr 23 '12 at 10:04
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  I tired on putty 0.62 and the above setting does not help. I tried to override XON, XOFF and with different values but nothing change.
  
  – Dennis C
  Nov 26 '12 at 1:42
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  This also works for nested SSH sessions using openssh as the 2nd, 3rd (etc) client
  
  – Felipe Alvarez
  Jun 1 '15 at 4:34
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Upvoting this answer as the best way to disable software flow control. For controlling terminal behaviour, the terminal emulator is the best place to configure it. Disabling XON/XOFF flow control in Putty means that when a pseudo-terminal is requested from a remote host, SSH servers will honour that setting when allocating the pseudo-terminal. See tools.ietf.org/html/rfc4254#section-6.2
  
  – Anthony Geoghegan
  Sep 7 '18 at 9:33
  
  
  

  
  
  
  

 | 
show 1 more comment

5

.bashrc example:

#

# Stop Putty from doing XOFF/XON with Ctrl-S/Ctrl-Q

# SOURCE: http://raamdev.com/recovering-from-ctrls-in-putty (Morgy, 7/14/08)

#

# stty ixany

# stty ixoff -ixon

### If needing to listen to Ctrl-S for some apps, use these two instead:

stty stop undef

stty start undef

share|improve this answer

answered Oct 1 '12 at 17:25

Jack HamiltonJack Hamilton

5111

add a comment | 

4

Open your .bash_profile and put:

stty -ixon

The value -xion doen't work for me. You can see the man entry: man stty.

share|improve this answer

edited Jul 9 '11 at 12:09

3498DB

15.8k114762

answered Jun 23 '10 at 18:06

FidsFids

411

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  +1 for stty -xion does not work on my centos, but stty -ixon works.
  
  – Jichao
  Dec 9 '10 at 16:18
  
  
  

  
  
  
  

add a comment | 

4

I've got the opposite problem. Every once in a while, the host sends an XOFF to PuTTY but never sends the corresponding XON to PuTTY. In this case, nothing you do to PuTTY (short of restarting it) will unwedge it. In this case, all keyboard input to the host is blocked, but the host can still send data to PuTTY.

Disabling flow control in PuTTY doesn't work.

The way to fix this problem is to use

stty -ixoff

in your .profile. This prohibits the host from sending XON/XOFF. Note that the names of the options are totally confusing. ixon/-ixon means enable/disable flow control on the client side (meaning that the client can't issue flow control), ixoff/-ixoff means enable/disable flow control on the host side (meaning the host can't issue flow control).

Btw, the ASCII code for Ctrl-S and XOFF are the same ASCII character (code 19, 0x13). There's no difference. The settings change the interpretation of that ASCII character.

share|improve this answer

edited Apr 28 '16 at 17:40

answered May 14 '13 at 17:13

Mark LakataMark Lakata

2,83611316

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Oh man, I've searched everywhere for an explanation for ixon and ixoff. Sending XON/XOFF from client to host makes sense. However, I'm still confused, in what situations does the host send to the client flow control XON/XOFF? I see "when the input queue is nearly empty/full"? Does this happen with modern computers, as in not connecting to slow printers? But what does that practically mean? What happens to the terminal UI?
  
  – CMCDragonkai
  Apr 28 '16 at 16:23
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Flow control works in both directions. A modern computer is always doing a million other things, and it can "lock up" doing critical activity. During this time, it can't service the serial port and the serial port will overflow unless the terminal shuts up. So the host sends XOFF to the terminal requesting it to stop sending. Once the pressure is off, the host sends XON. (btw, computer serial ports usually only have a small hardware buffer, say 16 bytes.) Even though this is ancient technology, anything that is not designed for real-time will occasionally "hang" so flow control is needed.
  
  – Mark Lakata
  Apr 28 '16 at 17:37
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  BTW, I have found cases where a tiny little 20 MHz microcontroller is able to overflow a 3 GHz host computer, but not vice versa. That is because the microcontroller is only doing one thing and designed with real-time in mind, while the host computer is not.
  
  – Mark Lakata
  Apr 28 '16 at 17:39
  

  
  
  
  

add a comment | 

0

Run this command in terminal to disable it for current session/add it to .bashrc for disabling it permanently

stty -ixon

share|improve this answer

answered 10 mins ago

Aldrin BennetAldrin Bennet

1

New contributor

Aldrin Bennet is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f124845%2fcan-you-disable-the-ctrl-s-xoff-keystroke-in-putty%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

33

Don't know about Putty, but you can use:

stty -ixon

on remote host, to disable START/STOP signals.

share|improve this answer

edited Feb 22 '11 at 11:42

answered Mar 27 '10 at 22:10

BartoszBartosz

44645

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks - any idea if or how this affects the console? Would it alter the behavior of shell programs? (The only thing I know about XON/XOFF is that it's used for serial flow control). Sounds like a good setting for .bash_profile.
  
  – Seth
  Mar 29 '10 at 16:57
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  That should be stty -ixon.
  
  – Oddthinking
  Feb 16 '11 at 1:44
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Sorry. Updated my post to fix the typo.
  
  – Bartosz
  Feb 22 '11 at 11:43
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  As I just commented to BlakBat on his answer, that makes ^S not send an XOFF, but it now puts me into i-search mode. Is there a way I can get bash (or PuTTY) just to discard any ^S? Even better would be if it could beep and/or flash at me ;o)
  
  – Owen Blacker
  Feb 14 '12 at 15:06
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  I've added stty -ixon to my profile scripts. I've read about 100 articles on how when you press CTRL+s by accident, all you have to do is CTRL+q to resume again...but I don't want my shell to intercept CTRL+s/q at all since I use them with vim quite a bit. Thank you so much for providing an answer nobody else seems to even consider.
  
  – andrew
  Mar 11 '12 at 8:46
  

  
  
  
  

add a comment | 

33

Don't know about Putty, but you can use:

stty -ixon

on remote host, to disable START/STOP signals.

share|improve this answer

edited Feb 22 '11 at 11:42

answered Mar 27 '10 at 22:10

BartoszBartosz

44645

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks - any idea if or how this affects the console? Would it alter the behavior of shell programs? (The only thing I know about XON/XOFF is that it's used for serial flow control). Sounds like a good setting for .bash_profile.
  
  – Seth
  Mar 29 '10 at 16:57
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  That should be stty -ixon.
  
  – Oddthinking
  Feb 16 '11 at 1:44
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Sorry. Updated my post to fix the typo.
  
  – Bartosz
  Feb 22 '11 at 11:43
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  As I just commented to BlakBat on his answer, that makes ^S not send an XOFF, but it now puts me into i-search mode. Is there a way I can get bash (or PuTTY) just to discard any ^S? Even better would be if it could beep and/or flash at me ;o)
  
  – Owen Blacker
  Feb 14 '12 at 15:06
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  I've added stty -ixon to my profile scripts. I've read about 100 articles on how when you press CTRL+s by accident, all you have to do is CTRL+q to resume again...but I don't want my shell to intercept CTRL+s/q at all since I use them with vim quite a bit. Thank you so much for providing an answer nobody else seems to even consider.
  
  – andrew
  Mar 11 '12 at 8:46
  

  
  
  
  

add a comment | 

Don't know about Putty, but you can use:

stty -ixon

on remote host, to disable START/STOP signals.

share|improve this answer

edited Feb 22 '11 at 11:42

answered Mar 27 '10 at 22:10

BartoszBartosz

44645

stty -ixon

share|improve this answer

edited Feb 22 '11 at 11:42

answered Mar 27 '10 at 22:10

BartoszBartosz

44645

answered Mar 27 '10 at 22:10

BartoszBartosz

44645

answered Mar 27 '10 at 22:10

BartoszBartosz

44645

28

The PuTTY solution:

1. before creating the session go navigate to Connection->SSH->TTY in the list.


2. in the "Mode" dropdown box, select IXON (nb: as of version 0.60, this list is not alphabetically ordered)


3. put "0" (zero) as the value of IXON.

Works as a charm, even if you open up a "GNU screen" on top of it, SSH to another host, or "su" to another user

If you're using GNU Bash, ctrl-S should allow you now to do a forward-search-history (aka: i-search)

You can see the difference in the output of "stty -a | grep -o ".ixon":
With putty configured it prints "-ixon", without " ixon"

share|improve this answer

edited Jan 11 '12 at 14:29

answered Jan 10 '12 at 15:11

BlakBatBlakBat

7351819

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Ok, that makes ^S not send an XOFF, but it now puts me into i-search mode. Is there a way I can get PuTTY (or bash) just to discard any ^S? Even better would be if it could beep and/or flash at me ;o)
  
  – Owen Blacker
  Feb 14 '12 at 15:05
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  To deactivate an action, you can bind ^S to nothing via bind '"C-s"'. This makes my PuTTY blink because the action is not mapped.
  
  – BlakBat
  Apr 23 '12 at 10:04
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  I tired on putty 0.62 and the above setting does not help. I tried to override XON, XOFF and with different values but nothing change.
  
  – Dennis C
  Nov 26 '12 at 1:42
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  This also works for nested SSH sessions using openssh as the 2nd, 3rd (etc) client
  
  – Felipe Alvarez
  Jun 1 '15 at 4:34
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Upvoting this answer as the best way to disable software flow control. For controlling terminal behaviour, the terminal emulator is the best place to configure it. Disabling XON/XOFF flow control in Putty means that when a pseudo-terminal is requested from a remote host, SSH servers will honour that setting when allocating the pseudo-terminal. See tools.ietf.org/html/rfc4254#section-6.2
  
  – Anthony Geoghegan
  Sep 7 '18 at 9:33
  
  
  

  
  
  
  

 | 
show 1 more comment

28

The PuTTY solution:

1. before creating the session go navigate to Connection->SSH->TTY in the list.


2. in the "Mode" dropdown box, select IXON (nb: as of version 0.60, this list is not alphabetically ordered)


3. put "0" (zero) as the value of IXON.

Works as a charm, even if you open up a "GNU screen" on top of it, SSH to another host, or "su" to another user

If you're using GNU Bash, ctrl-S should allow you now to do a forward-search-history (aka: i-search)

You can see the difference in the output of "stty -a | grep -o ".ixon":
With putty configured it prints "-ixon", without " ixon"

share|improve this answer

edited Jan 11 '12 at 14:29

answered Jan 10 '12 at 15:11

BlakBatBlakBat

7351819

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Ok, that makes ^S not send an XOFF, but it now puts me into i-search mode. Is there a way I can get PuTTY (or bash) just to discard any ^S? Even better would be if it could beep and/or flash at me ;o)
  
  – Owen Blacker
  Feb 14 '12 at 15:05
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  To deactivate an action, you can bind ^S to nothing via bind '"C-s"'. This makes my PuTTY blink because the action is not mapped.
  
  – BlakBat
  Apr 23 '12 at 10:04
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  I tired on putty 0.62 and the above setting does not help. I tried to override XON, XOFF and with different values but nothing change.
  
  – Dennis C
  Nov 26 '12 at 1:42
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  This also works for nested SSH sessions using openssh as the 2nd, 3rd (etc) client
  
  – Felipe Alvarez
  Jun 1 '15 at 4:34
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Upvoting this answer as the best way to disable software flow control. For controlling terminal behaviour, the terminal emulator is the best place to configure it. Disabling XON/XOFF flow control in Putty means that when a pseudo-terminal is requested from a remote host, SSH servers will honour that setting when allocating the pseudo-terminal. See tools.ietf.org/html/rfc4254#section-6.2
  
  – Anthony Geoghegan
  Sep 7 '18 at 9:33
  
  
  

  
  
  
  

 | 
show 1 more comment

The PuTTY solution:

1. before creating the session go navigate to Connection->SSH->TTY in the list.


2. in the "Mode" dropdown box, select IXON (nb: as of version 0.60, this list is not alphabetically ordered)


3. put "0" (zero) as the value of IXON.

Works as a charm, even if you open up a "GNU screen" on top of it, SSH to another host, or "su" to another user

If you're using GNU Bash, ctrl-S should allow you now to do a forward-search-history (aka: i-search)

You can see the difference in the output of "stty -a | grep -o ".ixon":
With putty configured it prints "-ixon", without " ixon"

share|improve this answer

edited Jan 11 '12 at 14:29

answered Jan 10 '12 at 15:11

BlakBatBlakBat

7351819

share|improve this answer

edited Jan 11 '12 at 14:29

answered Jan 10 '12 at 15:11

BlakBatBlakBat

7351819

answered Jan 10 '12 at 15:11

BlakBatBlakBat

7351819

answered Jan 10 '12 at 15:11

BlakBatBlakBat

7351819

5

.bashrc example:

#

# Stop Putty from doing XOFF/XON with Ctrl-S/Ctrl-Q

# SOURCE: http://raamdev.com/recovering-from-ctrls-in-putty (Morgy, 7/14/08)

#

# stty ixany

# stty ixoff -ixon

### If needing to listen to Ctrl-S for some apps, use these two instead:

stty stop undef

stty start undef

share|improve this answer

answered Oct 1 '12 at 17:25

Jack HamiltonJack Hamilton

5111

add a comment | 

5

.bashrc example:

#

# Stop Putty from doing XOFF/XON with Ctrl-S/Ctrl-Q

# SOURCE: http://raamdev.com/recovering-from-ctrls-in-putty (Morgy, 7/14/08)

#

# stty ixany

# stty ixoff -ixon

### If needing to listen to Ctrl-S for some apps, use these two instead:

stty stop undef

stty start undef

share|improve this answer

answered Oct 1 '12 at 17:25

Jack HamiltonJack Hamilton

5111

add a comment | 

.bashrc example:

#

# Stop Putty from doing XOFF/XON with Ctrl-S/Ctrl-Q

# SOURCE: http://raamdev.com/recovering-from-ctrls-in-putty (Morgy, 7/14/08)

#

# stty ixany

# stty ixoff -ixon

### If needing to listen to Ctrl-S for some apps, use these two instead:

stty stop undef

stty start undef

share|improve this answer

answered Oct 1 '12 at 17:25

Jack HamiltonJack Hamilton

5111

.bashrc example:

#

# Stop Putty from doing XOFF/XON with Ctrl-S/Ctrl-Q

# SOURCE: http://raamdev.com/recovering-from-ctrls-in-putty (Morgy, 7/14/08)

#

# stty ixany

# stty ixoff -ixon

### If needing to listen to Ctrl-S for some apps, use these two instead:

stty stop undef

stty start undef

share|improve this answer

answered Oct 1 '12 at 17:25

Jack HamiltonJack Hamilton

5111

answered Oct 1 '12 at 17:25

Jack HamiltonJack Hamilton

5111

answered Oct 1 '12 at 17:25

Jack HamiltonJack Hamilton

5111

4

Open your .bash_profile and put:

stty -ixon

The value -xion doen't work for me. You can see the man entry: man stty.

share|improve this answer

edited Jul 9 '11 at 12:09

3498DB

15.8k114762

answered Jun 23 '10 at 18:06

FidsFids

411

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  +1 for stty -xion does not work on my centos, but stty -ixon works.
  
  – Jichao
  Dec 9 '10 at 16:18
  
  
  

  
  
  
  

add a comment | 

4

Open your .bash_profile and put:

stty -ixon

The value -xion doen't work for me. You can see the man entry: man stty.

share|improve this answer

edited Jul 9 '11 at 12:09

3498DB

15.8k114762

answered Jun 23 '10 at 18:06

FidsFids

411

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  +1 for stty -xion does not work on my centos, but stty -ixon works.
  
  – Jichao
  Dec 9 '10 at 16:18
  
  
  

  
  
  
  

add a comment | 

Open your .bash_profile and put:

stty -ixon

The value -xion doen't work for me. You can see the man entry: man stty.

share|improve this answer

edited Jul 9 '11 at 12:09

3498DB

15.8k114762

answered Jun 23 '10 at 18:06

FidsFids

411

stty -ixon

share|improve this answer

edited Jul 9 '11 at 12:09

3498DB

15.8k114762

answered Jun 23 '10 at 18:06

FidsFids

411

edited Jul 9 '11 at 12:09

3498DB

15.8k114762

edited Jul 9 '11 at 12:09

3498DB

15.8k114762

answered Jun 23 '10 at 18:06

FidsFids

411

answered Jun 23 '10 at 18:06

FidsFids

411

4

I've got the opposite problem. Every once in a while, the host sends an XOFF to PuTTY but never sends the corresponding XON to PuTTY. In this case, nothing you do to PuTTY (short of restarting it) will unwedge it. In this case, all keyboard input to the host is blocked, but the host can still send data to PuTTY.

Disabling flow control in PuTTY doesn't work.

The way to fix this problem is to use

stty -ixoff

in your .profile. This prohibits the host from sending XON/XOFF. Note that the names of the options are totally confusing. ixon/-ixon means enable/disable flow control on the client side (meaning that the client can't issue flow control), ixoff/-ixoff means enable/disable flow control on the host side (meaning the host can't issue flow control).

Btw, the ASCII code for Ctrl-S and XOFF are the same ASCII character (code 19, 0x13). There's no difference. The settings change the interpretation of that ASCII character.

share|improve this answer

edited Apr 28 '16 at 17:40

answered May 14 '13 at 17:13

Mark LakataMark Lakata

2,83611316

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Oh man, I've searched everywhere for an explanation for ixon and ixoff. Sending XON/XOFF from client to host makes sense. However, I'm still confused, in what situations does the host send to the client flow control XON/XOFF? I see "when the input queue is nearly empty/full"? Does this happen with modern computers, as in not connecting to slow printers? But what does that practically mean? What happens to the terminal UI?
  
  – CMCDragonkai
  Apr 28 '16 at 16:23
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Flow control works in both directions. A modern computer is always doing a million other things, and it can "lock up" doing critical activity. During this time, it can't service the serial port and the serial port will overflow unless the terminal shuts up. So the host sends XOFF to the terminal requesting it to stop sending. Once the pressure is off, the host sends XON. (btw, computer serial ports usually only have a small hardware buffer, say 16 bytes.) Even though this is ancient technology, anything that is not designed for real-time will occasionally "hang" so flow control is needed.
  
  – Mark Lakata
  Apr 28 '16 at 17:37
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  BTW, I have found cases where a tiny little 20 MHz microcontroller is able to overflow a 3 GHz host computer, but not vice versa. That is because the microcontroller is only doing one thing and designed with real-time in mind, while the host computer is not.
  
  – Mark Lakata
  Apr 28 '16 at 17:39
  

  
  
  
  

add a comment |