Billy<p>Any idea why xon/xoff flow control would suddenly become enabled? I am working on a remote Ubuntu host, and suddenly ctrl-s is borderline malicious. I use emacs, and I don't even think about ctrl-s before I do it, so the xon/xoff flow control is very disruptive. The machine uptime is 18 days, and this has happened in the last hour. I haven't messed with any network config. I guess a system administrator could have updated packages. Could that have enabled xon/xoff flow control?</p><p><a href="https://mountains.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a> <a href="https://mountains.social/tags/flowcontrol" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>flowcontrol</span></a> <a href="https://mountains.social/tags/xon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>xon</span></a> <a href="https://mountains.social/tags/xoff" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>xoff</span></a> <a href="https://mountains.social/tags/emacs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>emacs</span></a> <a href="https://mountains.social/tags/uptime" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>uptime</span></a> <a href="https://mountains.social/tags/ssh" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ssh</span></a></p>