suboptimal defaults in awstats (LogFile and LogFormat)
Bug #319871 reported by
Andreas Olsson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
awstats (Debian) |
Fix Released
|
Unknown
|
|||
awstats (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Binary package hint: awstats
In a fresh install of awstats, including jaunty, the default /etc/awstats/
LogFile=
LogFormat=4
Wouldn't it make more sence to instead use the following?
LogFile=
LogFormat=1
If you install a new web server today it will most likely be an Apache 2.x.
The default apache2 configuration in Ubuntu uses the combined log format (LogFormat=1)
While parsing a "combined" access log as the common format (LogFormat=4) kinda works, it won't give you as much information.
Changed in awstats (Debian): | |
status: | Unknown → New |
Changed in awstats (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in awstats (Ubuntu): | |
importance: | Undecided → Low |
Changed in awstats (Debian): | |
status: | New → Fix Released |
To post a comment you must log in.
From duplicate:
/var/log/ apache2/ access. log is only accessible for root.adm, but the cronjob of awstats runs as www-data, so awstats can't access the logfile and won't work.