Wundy wrote:
Currently I have completed my script and tested it.
it reads access.log , formats it and dumps it into a postgres db
I also upgraded to squid3.0PRE5 ( the debian standerd package, will suffice
for current testing )
Sorry wundy. I have to disagree. PRE5 is seriously buggy package.
Currently I have completed my script and tested it.
it reads access.log , formats it and dumps it into a postgres db
I also upgraded to squid3.0PRE5 ( the debian standerd package, will suffice
for current testing )
I downloaded the 2.7 source files and checked the code for logfile-daemon
but I
On fre, 2008-05-16 at 01:52 +1200, Amos Jeffries wrote:
> As stated elsewhere 2.6 now supports custom logging daemons. Which would
> be the easiest and involve less experimental code.
That's a 2.7 feature. Not found in 2.6.
Regards
Henrik
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 ha
You could write one yourself, as squid supports a 'logfile' daemon,
or try mysar. It reads the squid logfile and import all content into a
mysql database.
get it at mysar.sf.net
and the fast C code version at www.polaco.pro.br/mysar
Wundy wrote:
Hi!
I currently have a transparent squid in plac
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 variou
