John covici schrieb:
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?
Maybe the definition of Logfile for httpd has changed upstream. Why
don't you just do
echo 'Logfile =
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
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
John Covici schrieb:
Package: logwatch
Version: 7.3-1
Severity: normal
I have some log files in a different directory than /var/log
and a previous version of logwatch responded to --logdir
option and used those files. the only thing in that directory
is appache logs. Now when I run
/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.
on Friday 08/18/2006 Willi Mann([EMAIL PROTECTED]) wrote
John Covici schrieb:
Package: logwatch
Version:
Package: logwatch
Version: 7.3-1
Severity: normal
I have some log files in a different directory than /var/log
and a previous version of logwatch responded to --logdir
option and used those files. the only thing in that directory
is appache logs. Now when I run it from the cron job, it uses
6 matches
Mail list logo
