Your message dated Tue, 19 Jan 2010 19:41:30 +0100
with message-id <[email protected]>
and subject line Re: Bug#565875: sarg: Automatic cleanup needed
has caused the Debian Bug report #565875,
regarding sarg: Automatic cleanup needed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
565875: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565875
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sarg
Version: 2.2.5-2
Severity: wishlist
SARG is never cleaning up its files, and it is not an easy task to write a
cronjob to do so because of its special (you said "broken"?) directory
structure.
It is a problem because it generates a lot of different files, up to filling
the inode table of /var in less than one month on my system.
Thanks
-- System Information:
Debian Release: 5.0.3
APT prefers proposed-updates
APT policy: (500, 'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages sarg depends on:
ii libc6 2.7-18lenny1 GNU C Library: Shared libraries
ii libgd2-xpm 2.0.36~rc1~dfsg-3+lenny1 GD Graphics Library version 2
sarg recommends no packages.
Versions of packages sarg suggests:
ii apache2 2.2.9-10+lenny6 Apache HTTP Server metapackage
ii apache2-mpm-prefor 2.2.9-10+lenny6 Apache HTTP Server - traditional n
ii libapache2-mod-php 5.2.6.dfsg.1-1+lenny4 server-side, HTML-embedded scripti
pn squid <none> (no description available)
pn squidguard <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Jerome,
please see the 'lastlog' configuration option in your sarg.conf. It should
resolve your issue with reports in /var/www. If the number of files in reports
you need to keep exceeds the limit of your filesystem I suggest you prepare a
filesystem with an higher number of inodes. See the man file for the specific
filesystem tool for directions.
Regards,
L
Il giorno 19/gen/2010, alle ore 09.57, Jerome Warnier ha scritto:
> SARG is never cleaning up its files, and it is not an easy task to write a
> cronjob to do so because of its special (you said "broken"?) directory
> structure.
> It is a problem because it generates a lot of different files, up to filling
> the inode table of /var in less than one month on my system.
--
Luigi Gangitano -- <[email protected]> -- <[email protected]>
GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972 C24A F19B A618 924C 0C26
--- End Message ---
