Article View: comp.bugs.4bsd
Article #144Re: A ping question and the infamous "sendto: No buffer space available" message
From: Timothy Fossum
Date: Wed, 06 Dec 1989 22:56
Date: Wed, 06 Dec 1989 22:56
13 lines
1476 bytes
1476 bytes
This phenomenon occurred frequently with our point-to-point SLIP line. When the other end went down, the modem lost carrier and the driver closed down the line PERMANENTLY. Our fix was to ignore loss of carrier, since the higher- level network code will know if the connection is lost when it fails to see ACKs. Also, when the carrier reappears, the line comes back without fuss (since the driver never recognized it was down in the first place). This also makes it unnecessary for operations personnel to respond to a downed line. I've looked at 4.3Tahoe and straight 4.3BSD, and they seem to have the same problem. I'll be glad to post diffs if anyone wants them... -- ----------------------------------------------------------------------------- Timothy Fossum -- UW-Parkside -- Wood Road, Box No. 2000 -- Kenosha, WI 53141 Department of Applied Computer Science -- fossum@vacs.uwp.wisc.edu (Internet)
Technical Details
Message-ID:
<1367@uwm.edu>Path:
arc1-ca.pugleaf.net!utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!vacs.uwp.wisc.edu!fossumReferences:
<1989Dec1.102932.15678@larouch.uucp> <4388@helios.ee.lbl.gov>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!vacs.uwp.wisc.edu!fossum From: fossum@vacs.uwp.wisc.edu (Timothy Fossum) Newsgroups: comp.bugs.4bsd Subject: Re: A ping question and the infamous "sendto: No buffer space available" message Keywords: sendto Message-ID: <1367@uwm.edu> Date: 6 Dec 89 22:56:29 GMT References: <1989Dec1.102932.15678@larouch.uucp> <4388@helios.ee.lbl.gov> Sender: news@uwm.edu Reply-To: fossum@vacs.uwp.wisc.edu (Timothy Fossum) Organization: University of Wisconsin - Parkside Lines: 13