This is a prime example of why file destinations (all destinations really) should follow the time_reap() and time_reopen() options. I just wanted to emphasize that I would like to see this on the to-do list. Is there a published "to-do list" or "wish list"? Evan. liuruihong wrote:
I have resolved the problem by increasing the maximum file handle,
Thanks all the person who helped me.
_____
发件人: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] 代表 liuruihong 发送时间: 2007年9月26日 11:22 收件人: 'Syslog-ng users' and developers' mailing list' 主题: [syslog-ng] 答复: WAS: why dose the usage of mem by syslog-ng keepgrowing? NOW: FAQ update
I will use 'ulimit -n A 'to increase the maximum file handles,
but is there a limit about the A ?
---------- syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] Nate Campi 2007年9月26日 4:27 Syslog-ng users' and developers' mailing list [syslog-ng] WAS: why dose the usage of mem by syslog-ng keepgrowing? NOW: FAQ update
On Tue, Sep 25, 2007 at 10:07:27AM +0200, Balazs Scheidler wrote:
The workaround then would be to increase the maximum file handles
(ulimit -n) before starting syslog-ng, the best is to put this in the
init script.
I just realized the FAQ doesn't mention ulimit anywhere. Fixed:
http://www.campin.net/syslog-ng/faq.html#ulimit
I've always had to do this on all my busy loghosts, should have gone
into the performance section of the FAQ long ago.
------------------------------------------------------------------------
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
-- Evan Rempel erempel@uvic.ca Senior Programmer Analyst 250.721.7691 Computing Services University of Victoria