Jonathan Stone <jonathan@dsg.stanford.edu> wrote:

> OTOH, all evening I have been busily issuing `pings' to try to keep my
> wifi alive, fully expecting to see ping -f eventualy return "No buffer
> space available".  How long has ping been returning ENOBUFS? Or ttcp -U?
> I'd guess 20-odd years.  If the people (all too often also-rans) who
> go to standards bodies stupidly mandated no errors for blocking
> send()s, 

Don't forget it's also what we have in our man page. It took me quite
some time to discover why send(2) was returning ENOBUFS.

> is there some way we can preserve traditional BSD
> compatibility on a per-process/per-app basis? A setsockopt(), maybe)?

A setsockopt for that would be great. I can do that if nobody complain.

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@netbsd.org