|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Victor Duchovni (Victor.Duchovni
MorganStanley.com)
Date: Thu Nov 01 2007 - 11:52:11 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Nov 01, 2007 at 09:37:25AM -0700, Andreas Grimm wrote:
> You're right. max_connections makes sense only to unix-stream. As
> pointed out earlier log_fifo_size does the trick on my server. Sorry
> for the hopwash i wrote. Increasing log_fifo_size in the options solves
> it. I read the TUNING_README too, and think that would help others if
> this will be mentioned somewhere.
Where are you sending your logs? Mine all go to local files, and I've had
no need for log_fifo_size, which seems to be applicable to forwarding
to other syslog-ng servers over TCP. Are you forwarding log entries
to a remote server via TCP? On mail servers I only log to local files
(rotated hourly) and collect these out of band (after local compression).
I thought that output queue overflow leads to dropped messages, not
blocking, but I could be wrong about that. Are you sure that a lower
value causes performance issues rather than perhaps lost messages?
--
Viktor.
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.
To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:majordomo
postfix.org?body=unsubscribe%20postfix-users>
If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]