But what is strange is that it did actually work in a slightlyolder
version and has stopped now. So does this mean that there is no way
to process those log files?
on Sunday 08/20/2006 Willi Mann([EMAIL PROTECTED]) wrote
> John covici schrieb:
> > /usr/sbin/logwatch --logdir /var/www/vhosts/wlym.com/statistics/logs
> >
> > Within that directory are only logs of apache2 access_log.* and
> > error_log.* and similarly named logs for ssl.
> >
>
> So your apache logfiles' full path is like
>
> /var/www/vhosts/wlym.com/statistics/logs/access_log ?
>
> This will only work if your configuration for the http logfile contains
> access_log (as oposed to apache/access.log). The code that's responsible
> for that, reads like:
>
> foreach my $dir ("$Config{'logdir'}/", "/var/adm/", "/var/log/", "") {
> @TempLogFileList = reverse(glob($dir . $ReadConfigValues[$i]));
> last if (@TempLogFileList && (-e $TempLogFileList[0]));
> }
>
> and that would explain why it seems to you as it would use /var/log.
>
> If this is not the problem, please send the debug output:
>
> logwatch --debug 10 --other options--
>
> Willi
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
