Have you tried playing with:
kern.ipc.maxsockbuf: 262144
kern.ipc.sockbuf_waste_factor: 8
kern.ipc.maxsockets: 4136
The first one looks particularly interesting.
--Renaud
----- Original Message -----
From: "Len Conrad" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 20, 2001 6:28 AM
Subject: postfix: No buffer space available
> Sorry to bother you hackers again, but two submissions to -questions
> got no response so it looks like another scaleability issue on you
> people can handle :
>
> ================
>
> On a very busy postfix relay hub, we're seeing this:
>
> Feb 19 15:00:16 imgate2 postfix/smtpd[323]: fatal: socket: No buffer
> space available
>
> Feb 19 15:00:17 imgate2 postfix/smtp[684]: fatal: socket: No buffer
> space available
>
> Can we fix this with a systcl write?
>
> The server already has:
>
> # sysctl -a | grep maxfile
> kern.maxfiles: 16384
> kern.maxfilesperproc: 16384
>
> ... which fixed "fatal: too many files open" pb for this client last
> November.
>
> btw, Wietse Venema himself asked me to be informed of how I manage to
> tweak FreeBSD to handle this apparent scaleability issue.
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
