Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.bugs.4bsd
Subject: Re: networking bug?
Message-ID: <4611@mimsy.UUCP>
Date: Sun, 30-Nov-86 11:33:17 EST
Article-I.D.: mimsy.4611
Posted: Sun Nov 30 11:33:17 1986
Date-Received: Sun, 30-Nov-86 21:03:54 EST
References: <742@rosevax.Rosemount.COM> <235@rust.dec.com>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 29
Keywords: out of buffer space

>In article <742@rosevax.Rosemount.COM> dave@rosevax.Rosemount.COM
(Dave Marquardt) writes:
>>I've got a problem.  We have a VAX-11/785 running 4.2BSD, and every
>>two weeks or so, telnet and rlogin stop working. ... In checking out
>>the problem, I tried using telnet from the VAX to another machine,
>>and got this message: Out of buffer space.

In article <235@rust.dec.com>, sweeney@rust.dec.com (Glenn Sweeney) writes:
>This problem exists because the system is failing to properly release
>mbufs after they are used.

I doubt this:  A stock 4.2BSD system will panic with `panic: exit:
m_getclr' very soon after running out of mbufs.  There is at least
one other place in a 4.2 kernel that generates `ENOBUFS' errors,
and that is in the PSN (nee IMP) code in /sys/netimp.

The workaround (increasing NMBCLUSTERS) may still be useful on a
very busy system, where it is indeed possible to run out of space
(and soon panic).  But if you have a connection to a PSN, see if
perhaps your routing tables have become confused.  `netstat -r'
prints the kernel's routing tables.

(Better yet, convert to 4.3BSD and fix all those lurking bugs at
once.  It seems significant that only a handful of fixes have been
posted for 4.3BSD since its release, whereas 4.2 generated a
veritable flood. . . .)
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690)
UUCP:	seismo!mimsy!chris	ARPA/CSNet:	chris@mimsy.umd.edu