What is the (preferred) way to figure out how much data is waiting
on the receive buffer on a socket? I'm running largish >1M
receive buffers and would like to log a warning message if the
buffers ever get used near-full.
Pete
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
Hi,
I allready asked this about one year ago and now I'm asking this again:
Does ppp now support client-callback?
Does mpd support client-callback?
Does anybody know another ppp-software wich supports that?
bye,
--
--
--
E-mail: [EMAIL PROTECTED]
--
Hi Folks,
Luigi got ahold of me and straightened me out on the fxp driver.
There is a problem though. If you generate a LOT of ARP traffic
on a FreeBSD box (-STABLE) you can run out of mbufs. I'm looking into this
presently
and will tell you if I find anything useful to be don
Steve Fettig wrote:
>
> I recently set up an NFS server to run daily backups on. The server was
> built using an old P150 w/ 90 MB of ram and a 6GB hard drive. (All
> servers in this experiment are set up using FBSD 4.6.2 and the client is
> a Mac PowerBook G4 running Mac OS X.) Attached to
Hi Folks,
I note that in -STABLE, in the file dev/if_fxp.c, the routine fxp_start()
calls bpf_mtap() a few lines before the end of the function. There is no
associated
"free" with this call. It looks like fxp_intr_body() is supposed to free
transmitted
packets, but I'm not sure this i
