IMO, I think this area of dev should be revisited before 4.9-RELEASE.
Because when I brought it down to 4.8-RELEASE via cvsup, it has not failed
yet. It usually fails around 12 hrs from boot. And it has been 14+ hours now
running very fine.
One thing I noticed though... it seems that over time,
[EMAIL PROTECTED] writes:
This is serious. I have just cvsuped stable-supfile again and did all
necessary steps re kernel/world. It is still having this problem. Anybody
stumbled accross the same? Should I just reinstall back to 4.8-RELEASE?
Because I got another identical hardware/machine
Yes, exact kernel configurations too. To be specific, I just copy/pasted the
extra options plus the pseudo-device gre. And, yes. The same, on a 256MB
machine.
I have also tried the advice of Colin to set the sysctl :
net.inet.raw.recvspace=131072
net.inet.raw.maxdgram=8192
-RELEASE.
Also, netstat -m results is nowhere near the kernel max values.
Thanks in advance.
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, September 11, 2003 3:47 PM
Subject: sendto: buffer space not available
Hi,
I have this 4.9-PRERELEASE proxy
, test pings reports a sendto: buffer space not
available. I already have the following in my kernel config:
options MAXDSIZ=(256*1024*1024)
options MAXSSIZ=(256*1024*1024)
options DFLDSIZ=(256*1024*1024)
options NMBCLUSTERS=131072
Should I need to edit
