Re: equivalent flag or code to MSG_MORE in NetBSD?

There is an ancient BSD ioctl(2) which might cover this case: FIONREAD. The point of it back in the day was to be able to know just how much data could be read from a file descriptor (e.g., from TTY input buffers) without blocking. Erik Fair

Re: Running out of buffers?

> On Apr 27, 2018, at 15:58, Robert Elz > wrote: > >Date:Fri, 27 Apr 2018 21:34:49 +0100 >From:Roy Marples > >Message-ID:

Re: running out of file descriptors

user." I’ve had to contend with our assumed limits by significantly raising the per-process soft limits for programs like pkgsrc/www/privoxy wherein descriptor use is proportional to traffic/clients rather than to number of processes. something to consider, Erik Fair &g

Re: Potentially undesirable behavior with apropos(1)

I can probably use that dictionary to decide what to > stem and what not to stem. > > - > Abhinav In principle a lot of technical names are marked up in mandoc as “.Tn foo” which might provide a good list of words to “not stem.” Erik Fair

Re: building current - signal 6

/make/* shows possibilities … Perhaps turning on some make debug options will reveal more. Erik Fair > On May 3, 2016, at 16:59, Riccardo Mottola <riccardo.mott...@libero.it> wrote: > > Hi, > > when I build current on amd64, my build fails with: > > #

Re: No buffer space available

On Sep 1, 2014, at 01:46 , Michael van Elst mlel...@serpens.de wrote: t...@hamartun.priv.no (Tom Ivar Helbekkmo) writes: Sep 1 09:32:49 barsoom openvpn[2896]: write UDPv4: No buffer space available (code=55) This doesn't necessarily mean that the buffer space is too small. It often also

Re: No buffer space available

Network hangs are insidious. [old fart story time] The headscratcher for me was the one in the 1990's at apple.com (when apple.com was a DEC VAX-8650 running 4.3BSD) that led me to discover TCP_SYN attacks and report that to the CERT two years before panix.com was attacked in the same way.