Package: sarg
Version: 2.2.2-1
Followup-For: Bug #369693
The squid access.log is rotated by cron.daily/logrotate. Because of how
run-parts work
cron.daily/sarg is started after logrotate. The default sarg.conf file looks
at the access log
/var/log/squid/access.log. It seems to me that this means that the default is
to report on a log
file that will probably have almost nothing in it because all the access logs
would have been just
rotated out.
Wouldn't it be better to remove /etc/cron.{daily,weekly,monthly}/sarg and
instead create something
in /etc/cron.d like this.
---
5 0 * * * root test -x /usr/sbin/sarg-reports && /usr/sbin/sarg-reports daily
15 0 * * 7 root test -x /usr/sbin/sarg-reports && /usr/sbin/sarg-reports weekly
30 0 1 * * root test -x /usr/sbin/sarg-reports && /usr/sbin/sarg-reports
monthly
---
Or perhaps there should be no cron entries at all, and just provide a notice
with debconf
telling users that they need to configure sarg and provide some sample scripts
in the docs folder.
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages sarg depends on:
ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries
ii libgd2-noxpm 2.0.33-5.2 GD Graphics Library version 2 (wit
sarg recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
