<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ctrl + s caused terminal hangs in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758044#M784909</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;# stty -a&lt;BR /&gt;speed 9600 baud; line = 0;&lt;BR /&gt;rows = 24; columns = 90&lt;BR /&gt;min = 1; time = 0;&lt;BR /&gt;intr = ^C; quit = ^\; erase = ^H; kill = ^U&lt;BR /&gt;eof = ^D; eol = ^@; eol2 &lt;UNDEF&gt;; swtch &lt;UNDEF&gt;&lt;BR /&gt;stop = ^S; start = ^Q; susp &lt;UNDEF&gt;; dsusp &lt;UNDEF&gt;&lt;BR /&gt;werase &lt;UNDEF&gt;; lnext &lt;UNDEF&gt;&lt;BR /&gt;parenb -parodd cs7 -cstopb hupcl -cread -clocal -loblk -crts&lt;BR /&gt;-ignbrk brkint ignpar -parmrk -inpck istrip -inlcr -igncr icrnl -iuclc&lt;BR /&gt;ixon -ixany ixoff -imaxbel -rtsxoff -ctsxon -ienqak&lt;BR /&gt;isig icanon -iexten -xcase echo echoe echok -echonl -noflsh&lt;BR /&gt;-echoctl -echoprt -echoke -flusho -pendin&lt;BR /&gt;opost -olcuc onlcr -ocrnl -onocr -onlret -ofill -ofdel -tostop&lt;BR /&gt;&lt;BR /&gt;Q1) How to disable ctrl + s &amp;amp; ctrl + q?&lt;BR /&gt;Q2) What is the content after parenb used for?&lt;BR /&gt;&lt;BR /&gt;regards.&lt;/UNDEF&gt;&lt;/UNDEF&gt;&lt;/UNDEF&gt;&lt;/UNDEF&gt;&lt;/UNDEF&gt;&lt;/UNDEF&gt;</description>
    <pubDate>Thu, 23 Mar 2006 22:53:23 GMT</pubDate>
    <dc:creator>Ngoh Chean Siung</dc:creator>
    <dc:date>2006-03-23T22:53:23Z</dc:date>
    <item>
      <title>ctrl + s caused terminal hangs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758039#M784904</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I accidentally press ctrl + s and the terminal that I login just hangs there. Luckily I able to logout after pressing ctrl + d (I think shld be used to logout).&lt;BR /&gt;&lt;BR /&gt;Q1) What is the action after pressing ctrl + s? How to disable this key combination?&lt;BR /&gt;&lt;BR /&gt;Q2) Where can I get a list of all the key combination functionality?&lt;BR /&gt;&lt;BR /&gt;regards</description>
      <pubDate>Thu, 23 Mar 2006 21:42:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758039#M784904</guid>
      <dc:creator>Ngoh Chean Siung</dc:creator>
      <dc:date>2006-03-23T21:42:00Z</dc:date>
    </item>
    <item>
      <title>Re: ctrl + s caused terminal hangs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758040#M784905</link>
      <description>A CTRL-s will stop information from scrolling.  A CTRL-q will continue it.</description>
      <pubDate>Thu, 23 Mar 2006 21:46:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758040#M784905</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2006-03-23T21:46:29Z</dc:date>
    </item>
    <item>
      <title>Re: ctrl + s caused terminal hangs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758041#M784906</link>
      <description>You are a victim of XON/XOFF handshaking which is used when hardware handshaking of serial devices is not available. Ctrl-S (13h) is an XOFF; Ctrl-Q (11h) is an XON.&lt;BR /&gt;&lt;BR /&gt;Man ascii for the list of ASCII characters but there is no list as such for what you request. The behavior of a tty device is controlled by the termio data associated with the device. You must do a stty -a to see what the control characters are for your specific device.</description>
      <pubDate>Thu, 23 Mar 2006 22:05:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758041#M784906</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2006-03-23T22:05:10Z</dc:date>
    </item>
    <item>
      <title>Re: ctrl + s caused terminal hangs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758042#M784907</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;Control KeysControl Key stty Name Function Description&lt;BR /&gt;CTRL-C intr &lt;BR /&gt;&lt;BR /&gt;Stop current command&lt;BR /&gt;CTRL-D eof &lt;BR /&gt;&lt;BR /&gt;End of input&lt;BR /&gt;[CTRL-\] or [CTRL-|] quit &lt;BR /&gt;&lt;BR /&gt;Stop current command, if [CTRL-C] doesn't work&lt;BR /&gt;CTRL-S stop &lt;BR /&gt;&lt;BR /&gt;Halt output to screen&lt;BR /&gt;CTRL-Q  &lt;BR /&gt;&lt;BR /&gt;Restart output to screen&lt;BR /&gt;DEL or [CTRL-?] erase &lt;BR /&gt;&lt;BR /&gt;Erase last character&lt;BR /&gt;CTRL-U kill &lt;BR /&gt;&lt;BR /&gt;Erase entire command line&lt;BR /&gt;CTRL-Z susp &lt;BR /&gt;&lt;BR /&gt;Suspend current command &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.unix.org.ua/orelly/unix/ksh/ch01_09.htm" target="_blank"&gt;http://www.unix.org.ua/orelly/unix/ksh/ch01_09.htm&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;-Arun</description>
      <pubDate>Thu, 23 Mar 2006 22:08:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758042#M784907</guid>
      <dc:creator>Arunvijai_4</dc:creator>
      <dc:date>2006-03-23T22:08:52Z</dc:date>
    </item>
    <item>
      <title>Re: ctrl + s caused terminal hangs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758043#M784908</link>
      <description>Arunvijai's answers, while the default, would get an incorrect mark if I were giving the test because all of those values can be changed "on the fly". The only way to know is to ask the device node itself either through the stty command or an ioctl() call.</description>
      <pubDate>Thu, 23 Mar 2006 22:16:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758043#M784908</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2006-03-23T22:16:33Z</dc:date>
    </item>
    <item>
      <title>Re: ctrl + s caused terminal hangs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758044#M784909</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;# stty -a&lt;BR /&gt;speed 9600 baud; line = 0;&lt;BR /&gt;rows = 24; columns = 90&lt;BR /&gt;min = 1; time = 0;&lt;BR /&gt;intr = ^C; quit = ^\; erase = ^H; kill = ^U&lt;BR /&gt;eof = ^D; eol = ^@; eol2 &lt;UNDEF&gt;; swtch &lt;UNDEF&gt;&lt;BR /&gt;stop = ^S; start = ^Q; susp &lt;UNDEF&gt;; dsusp &lt;UNDEF&gt;&lt;BR /&gt;werase &lt;UNDEF&gt;; lnext &lt;UNDEF&gt;&lt;BR /&gt;parenb -parodd cs7 -cstopb hupcl -cread -clocal -loblk -crts&lt;BR /&gt;-ignbrk brkint ignpar -parmrk -inpck istrip -inlcr -igncr icrnl -iuclc&lt;BR /&gt;ixon -ixany ixoff -imaxbel -rtsxoff -ctsxon -ienqak&lt;BR /&gt;isig icanon -iexten -xcase echo echoe echok -echonl -noflsh&lt;BR /&gt;-echoctl -echoprt -echoke -flusho -pendin&lt;BR /&gt;opost -olcuc onlcr -ocrnl -onocr -onlret -ofill -ofdel -tostop&lt;BR /&gt;&lt;BR /&gt;Q1) How to disable ctrl + s &amp;amp; ctrl + q?&lt;BR /&gt;Q2) What is the content after parenb used for?&lt;BR /&gt;&lt;BR /&gt;regards.&lt;/UNDEF&gt;&lt;/UNDEF&gt;&lt;/UNDEF&gt;&lt;/UNDEF&gt;&lt;/UNDEF&gt;&lt;/UNDEF&gt;</description>
      <pubDate>Thu, 23 Mar 2006 22:53:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758044#M784909</guid>
      <dc:creator>Ngoh Chean Siung</dc:creator>
      <dc:date>2006-03-23T22:53:23Z</dc:date>
    </item>
    <item>
      <title>Re: ctrl + s caused terminal hangs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758045#M784910</link>
      <description>The answer to these questions is as close as a man stty. stty -ixon disables XON/XOFF flow control. parenb means generate a parity bit before sending a character and expect a parity bit when receiving a character.</description>
      <pubDate>Thu, 23 Mar 2006 23:16:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758045#M784910</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2006-03-23T23:16:48Z</dc:date>
    </item>
    <item>
      <title>Re: ctrl + s caused terminal hangs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758046#M784911</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;How to make it permanent and apply to all the login terminals? Because this setting is only take affect on the current login terminal that you are using.&lt;BR /&gt;&lt;BR /&gt;regards.</description>
      <pubDate>Fri, 24 Mar 2006 00:52:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758046#M784911</guid>
      <dc:creator>Ngoh Chean Siung</dc:creator>
      <dc:date>2006-03-24T00:52:39Z</dc:date>
    </item>
    <item>
      <title>Re: ctrl + s caused terminal hangs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758047#M784912</link>
      <description>Hello, &lt;BR /&gt;&lt;BR /&gt;You can add this entry to your .profile at $HOME/.profile. It will executed at the time of your login. &lt;BR /&gt;&lt;BR /&gt;-Arun</description>
      <pubDate>Fri, 24 Mar 2006 01:14:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758047#M784912</guid>
      <dc:creator>Arunvijai_4</dc:creator>
      <dc:date>2006-03-24T01:14:34Z</dc:date>
    </item>
    <item>
      <title>Re: ctrl + s caused terminal hangs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758048#M784913</link>
      <description>Your questions are all related with stty setting. Refer man page of stty.&lt;BR /&gt;&lt;BR /&gt;To make permanent then configure in $HOME/.profile or /etc/profile.&lt;BR /&gt;&lt;BR /&gt;--&lt;BR /&gt;Muthu</description>
      <pubDate>Fri, 24 Mar 2006 01:23:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758048#M784913</guid>
      <dc:creator>Muthukumar_5</dc:creator>
      <dc:date>2006-03-24T01:23:09Z</dc:date>
    </item>
    <item>
      <title>Re: ctrl + s caused terminal hangs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758049#M784914</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;May I know what is below option used for?&lt;BR /&gt;&lt;BR /&gt;      isig (-isig)             Enable (disable) the checking of characters&lt;BR /&gt;                               against the special control characters INTR&lt;BR /&gt;                               and QUIT.&lt;BR /&gt;&lt;BR /&gt;regards.</description>
      <pubDate>Fri, 24 Mar 2006 01:47:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758049#M784914</guid>
      <dc:creator>Ngoh Chean Siung</dc:creator>
      <dc:date>2006-03-24T01:47:37Z</dc:date>
    </item>
    <item>
      <title>Re: ctrl + s caused terminal hangs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758050#M784915</link>
      <description>Hello, &lt;BR /&gt;&lt;BR /&gt;isig (-isig) Enable (disable) the checking of characters&lt;BR /&gt;against the special control characters INTR&lt;BR /&gt;and QUIT.&lt;BR /&gt;&lt;BR /&gt;"isig" is part of local mode flags, &lt;BR /&gt;&lt;BR /&gt;Local mode flags (lflags) affect various and sundry characteristics of terminal processing. Historically the term "local" pertained to new job control features implemented by Jim Kulp on a  Pdp 11/70 at  IIASA. Later the driver ran on the first  VAX at Evans Hall, UC Berkeley, where the job control details were greatly modified but the structure definitions and names remained essentially unchanged. The second interpretation of the â  lâ   in lflag is â  â  line discipline flagâ  â   which corresponds to the  c_lflag of the  termios structure.&lt;BR /&gt;&lt;BR /&gt;-Arun &lt;BR /&gt;</description>
      <pubDate>Fri, 24 Mar 2006 01:52:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758050#M784915</guid>
      <dc:creator>Arunvijai_4</dc:creator>
      <dc:date>2006-03-24T01:52:36Z</dc:date>
    </item>
    <item>
      <title>Re: ctrl + s caused terminal hangs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758051#M784916</link>
      <description>It is used to check the action against ctr+c and ctr+d. By default it is like,&lt;BR /&gt;&lt;BR /&gt;isig which handles signal.&lt;BR /&gt;&lt;BR /&gt;--&lt;BR /&gt;Muthu</description>
      <pubDate>Fri, 24 Mar 2006 01:52:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758051#M784916</guid>
      <dc:creator>Muthukumar_5</dc:creator>
      <dc:date>2006-03-24T01:52:50Z</dc:date>
    </item>
    <item>
      <title>Re: ctrl + s caused terminal hangs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758052#M784917</link>
      <description>One more link, &lt;A href="http://www.tldp.org/HOWTO/Text-Terminal-HOWTO-18.html#local_mode" target="_blank"&gt;http://www.tldp.org/HOWTO/Text-Terminal-HOWTO-18.html#local_mode&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;-Arun</description>
      <pubDate>Fri, 24 Mar 2006 01:54:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758052#M784917</guid>
      <dc:creator>Arunvijai_4</dc:creator>
      <dc:date>2006-03-24T01:54:42Z</dc:date>
    </item>
    <item>
      <title>Re: ctrl + s caused terminal hangs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758053#M784918</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;At /etc/profile, there is 1 trap signal command to trap below signal.&lt;BR /&gt;1 - sighup (terminal line hangup)&lt;BR /&gt;2 - sigint (ctrl + c)&lt;BR /&gt;3 - sigquit (ctrl + \)&lt;BR /&gt;&lt;BR /&gt;To trap above signal, the syntax is trap 1 2 3. To disable the signal trap, the syntax is trap "" 1 2 3&lt;BR /&gt;&lt;BR /&gt;Question:&lt;BR /&gt;1) At /etc/profile, trap signal is disabled at the beginning and it was enabled before last few lines. What is the impact if I hv syntax stty -isig after trap 1 2 3? All the signals (1 2 3) will be disabled same as the syntax trap "" 1 2 3? You may refer to below /etc/profile for more details.&lt;BR /&gt;&lt;BR /&gt;Below is the content for /etc/profile:&lt;BR /&gt;# Ignore HUP, INT, QUIT now.&lt;BR /&gt;&lt;BR /&gt;        trap "" 1 2 3&lt;BR /&gt;.&lt;BR /&gt;.&lt;BR /&gt;.&lt;BR /&gt;&lt;BR /&gt;# Leave defaults in user environment.&lt;BR /&gt;&lt;BR /&gt;        trap 1 2 3&lt;BR /&gt;        set -u&lt;BR /&gt;        trap "echo 'logout'" 0&lt;BR /&gt;.&lt;BR /&gt;.&lt;BR /&gt;.&lt;BR /&gt;TERMINAL=`tty`&lt;BR /&gt;&lt;BR /&gt;export TERMINAL&lt;BR /&gt;&lt;BR /&gt;# Pause for users to read motd or any other messages&lt;BR /&gt;        stty -isig&lt;BR /&gt;        echo "Tap &lt;CR&gt; to continue ... \c"&lt;BR /&gt;        read ans&lt;BR /&gt;        stty isig&lt;BR /&gt;.&lt;BR /&gt;.&lt;BR /&gt;.&lt;BR /&gt;&lt;BR /&gt;regards.&lt;/CR&gt;</description>
      <pubDate>Fri, 24 Mar 2006 03:40:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758053#M784918</guid>
      <dc:creator>Ngoh Chean Siung</dc:creator>
      <dc:date>2006-03-24T03:40:50Z</dc:date>
    </item>
    <item>
      <title>Re: ctrl + s caused terminal hangs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758054#M784919</link>
      <description>You still don't quite understand. There is no way to make these changes permanent because any application can change them (and hopefully restore them to their values&lt;BR /&gt;as they were when the application was started.) For example, suppose the you wanted to disable SIGINT (default is Ctrl-C under HP-UX; &lt;DEL&gt; under other UNIX flavors -- but it could be any key) inside an application. One method would be to use a signal handler or trap that simply ignores SIGINT so that when , for example, Ctrl-C is pressed, it's simply ignored. However, another approach would be to change the interrupt key to an impossible value such as 377 octal.&lt;/DEL&gt;</description>
      <pubDate>Fri, 24 Mar 2006 10:14:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758054#M784919</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2006-03-24T10:14:37Z</dc:date>
    </item>
    <item>
      <title>Re: ctrl + s caused terminal hangs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758055#M784920</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I understand what you mean.&lt;BR /&gt;&lt;BR /&gt;But I just want to know whether stty -isig is function same as trap "" 123.&lt;BR /&gt;&lt;BR /&gt;regards.</description>
      <pubDate>Mon, 27 Mar 2006 20:21:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758055#M784920</guid>
      <dc:creator>Ngoh Chean Siung</dc:creator>
      <dc:date>2006-03-27T20:21:24Z</dc:date>
    </item>
    <item>
      <title>Re: ctrl + s caused terminal hangs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758056#M784921</link>
      <description>No, signal 1 = Hangup, signal 2 = Interrupt, and signal 3 = Quit whereas stty -isig means ignore SIGINT,SIGQUIT, and suspends.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 27 Mar 2006 20:53:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758056#M784921</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2006-03-27T20:53:39Z</dc:date>
    </item>
    <item>
      <title>Re: ctrl + s caused terminal hangs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758057#M784922</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Can I say that stty -isig will disable SIGINT and SIGQUIT which is same as the trap signal for signal 2 = Interrupt and signal 3 = Quit?&lt;BR /&gt;&lt;BR /&gt;regards.</description>
      <pubDate>Mon, 27 Mar 2006 21:06:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758057#M784922</guid>
      <dc:creator>Ngoh Chean Siung</dc:creator>
      <dc:date>2006-03-27T21:06:35Z</dc:date>
    </item>
    <item>
      <title>Re: ctrl + s caused terminal hangs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758058#M784923</link>
      <description>That much is true; however, you are thinking shell scripts and that is only part of the picture. For example, once a process is started, it can still redefine signal handlers and key functions. The signal handlers are always restored to as they were when the child process started BUT there is no guarantee that the key functions are just as they were. Well written programs will always restore the key functions to the original state BUT ...</description>
      <pubDate>Mon, 27 Mar 2006 21:10:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ctrl-s-caused-terminal-hangs/m-p/3758058#M784923</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2006-03-27T21:10:23Z</dc:date>
    </item>
  </channel>
</rss>

