[syslog-ng] Limit filesize

Hiren Patel patelhn at telkom.co.za
Fri May 25 08:38:53 CEST 2007


i agree with Kevin,

setting limits usually means you will start loosing logs when that limit
is reached, depending on the importance of these logs, it might be worth
setting up alerting to disk space shortage, and buy more disks if the
importance of the logs outweighs the cost of having them.

On Thu, 2007-05-24 at 23:19 -0500, K K wrote:
> On 5/24/07, janth at moldung.no <janth at moldung.no> wrote:
> > Is it possible to limit the size of each logfile when using the destinatin shown under?
> 
> If your OS has a ulimit restricting the maximum size of any one file
> (look under 'man setrlimit' for RLIMIT_FSIZE), you could use this
> kernel feature to restrict the largest file that can be created.  This
> wouldn't allow setting different limits for each destination.
> 
> Alternately, you could use a unique userid for the logs from each
> untrustworthy log source, and use the native OS quota enforcement to
> limit total disk space, but this is even more OS-dependent than are
> ulimits.
> 
> I prefer to have a separate monitor routine (e.g. HobbitMon), a daemon
> or cron job which watches filesystem free space and sends an alert if
> any one filesystem runs low.
> 
> Kevin
> _______________________________________________
> syslog-ng maillist  -  syslog-ng at lists.balabit.hu
> https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
> 
-- 
Hiren Patel

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This e-mail and its contents are subject to the Telkom SA Limited
e-mail legal notice available at 
http://www.telkom.co.za/TelkomEMailLegalNotice.PDF
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


More information about the syslog-ng mailing list