Matthew Dillon wrote:
>
> p.s. (on a different topic) I am also seeing serial stream corruption
> for serial console output. If I add a kernel printf() that generates
> a lot of output, I get most of it on the serial console plus a lot
> of other random garbage. Very weird.
I'
On Fri, Apr 28, 2000 at 01:01:38AM +0100, void wrote:
> > to places that have 2~3 minute lag. :)
>
> And make it sysctl-controllable, perhaps?
It is already tunable for years via ioctl
--
Andrey A. Chernov
<[EMAIL PROTECTED]>
http://nagual.pp.ru/~ache/
To Unsubscribe: send mail to [EMAIL PRO
On Thu, Apr 27, 2000 at 01:06:16AM -0500, Michael C . Wu wrote:
> On Thu, Apr 27, 2000 at 01:14:02AM +0400, Andrey A. Chernov scribbled:
> | I often notice processes hanging forever on exit's ttywait when TCP
> | connection dropped. Here is a patch I plan to commit which restrict
> | waiting for o
On Thu, Apr 27, 2000 at 01:14:02AM +0400, Andrey A. Chernov scribbled:
| I often notice processes hanging forever on exit's ttywait when TCP
| connection dropped. Here is a patch I plan to commit which restrict
| waiting for output drain by 3 minutes. Any comments, improvements or
| objections?
--
> There is a number of places this may occurse and all of them have no timeout
> by default. F.e. if some terminal shell hangs in exit's ttywait, comsat
> hangs on ttywrite and lots of comsats appearse after several hours. Alternative
> solution will be adding
>
> tp->t_timeout = 180 *
On Wed, Apr 26, 2000 at 02:22:47PM -0700, Matthew Dillon wrote:
> :I often notice processes hanging forever on exit's ttywait when TCP
>
> I think this is a good idea. I've seen processes stuck in ttywait
> forever too, usually when I'm using cu and the remote end is spewing
> all so
:I often notice processes hanging forever on exit's ttywait when TCP
:connection dropped. Here is a patch I plan to commit which restrict
:waiting for output drain by 3 minutes. Any comments, improvements or
:objections?
:
:--- kern_exit.c.bakSun Apr 16 23:35:55 2000
:+++ kern_exit.cT
