Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: Notesfiles $Revision: 1.6.2.17 $; site uokmet.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!ihnp4!inuxc!pur-ee!uiucdcs!uokmet!kwthomas From: kwthomas@uokmet.UUCP Newsgroups: net.bugs.2bsd Subject: Re: 11/73,2.9,large amounts of output,he Message-ID: <1500008@uokmet.UUCP> Date: Mon, 14-Jan-85 14:53:00 EST Article-I.D.: uokmet.1500008 Posted: Mon Jan 14 14:53:00 1985 Date-Received: Wed, 16-Jan-85 16:07:52 EST References: <13200002@txsil.UUCP> Lines: 34 Nf-ID: #R:txsil:13200002:uokmet:1500008:000:1394 Nf-From: uokmet!kwthomas Jan 14 13:53:00 1985 >Configuration: > PDP 11/73, 1MEG, Emulex cs01/16 lines, 2 RL02's (RLV controler) > 2.9BSD software >Problem: > when running 'yes jfdljfldjflsjfdsjflsdlfjdsjfsljdsdjlfjsljfds' > or any program that outputs large amounts of data to the terminal > and running several terminals ( > 2) together, the programs start > spitting out info that looks like the kernel stuff, i.e. garbage chars. > > If I touch the control-S (^S), and stop the output, then control-Q, > the output starts up ok again. Note, that the problem can come back > and that it doesn't happen to all terminals. If I start with 10 > running, by the next morning only 2 or 3 are left ok. > > If have UCB_CLIST defined and undefined. We have strange problems for a while with ^S and ^Q. When 3 or more people did a ^S to stop output, our system (PDP 11/44 with 2.9BSD) would freeze dead in its tracks. Checking the PC indicated that the operating system was spinning around in the idle() loop! Do a ^Q at any of the "offending" terminals would cause the system to come alive with no effects, other than loss of time on the clock (verified by checking clock time before performing tests). As it turned out, somewhere along the way, I had turned off "UCB_CLIST". When I defined it, the ^S problem went away. Kevin W. Thomas Univ. of Oklahoma School of Meteorology Norman, OK 73019 UUCP: ...!ctvax!uokvax!uokmet!kwthomas