Wundy wrote:
Hi!
I currently have a transparent squid in place that used squidguard as a
blocking filter.
squid version is 2.6 STABLE.
I would like to import the access.log into a database for safe keeping and
easy access with queries.
a request from the company I do the internschip with.
I have read various pieces that Squid3.0 would support this but I can't find
any solid info on it.
is it still in development ? and if so is it stable enough to try it ?
My other option would be to write a perl script that reads access.log and
imports it into the database.
I have a question with this. is it possible to read the access.log and
afterwards clear the file so that I can just read the entire file everytime
I sync the database ? how would squid react to this clearing ?
also Squid rotates the logfiles. I currently have logfile rotate set to 0 so
It wouldn't rotate then ? but everything gets logged to access.log.1 . Can I
still change this ?
The 3.x project is still in development.
http://devel.squid-cache.org/projects.html
As stated elsewhere 2.6 now supports custom logging daemons. Which would
be the easiest and involve less experimental code. And gets around those
rotation limits you noticed. The daemon support is also on the roadmap
for 3.x 'very, very soon now', so your daemon will be cross-version.
Amos
--
Please use Squid 2.6.STABLE20 or 3.0.STABLE5
