From owner-freebsd-current Wed Apr 26 15: 7:17 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 700D137B9C7; Wed, 26 Apr 2000 15:07:15 -0700 (PDT) Date: Wed, 26 Apr 2000 15:07:15 -0700 From: "Andrey A. Chernov" To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: Workaround for hanging on exit: patch for review Message-ID: <20000426150715.A29997@freebsd.org> References: <20000427011402.A7265@nagual.pp.ru> <200004262122.OAA97717@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <200004262122.OAA97717@apollo.backplane.com>; from dillon@apollo.backplane.com on Wed, Apr 26, 2000 at 02:22:47PM -0700 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 sorts of junk my way. 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 * hz; while initializing tp struct, but it is more radical than I suggest initially. Any ideas? -- Andrey A. Chernov http://nagual.pp.ru/~ache/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message