Il giorno gio, 03-02-2005 alle 23:12 +0100, Luigi Gangitano ha scritto:
> Can you please check if 2.0.3-1 resolved this issue? In 2.0.3 upstream
> rewrote squidguard log parsing.
>
> Executing the new version on the same data with the same configuration
> file would be perfect.
Yes, running new
severity 293118 important
thanks
Change of severity rationale: this bug limits sarg functionatily but
doesn't make it completely unusable and doesn't generate data loss in
any way.
Can you please check if 2.0.3-1 resolved this issue? In 2.0.3 upstream
rewrote squidguard log parsing.
Executing t
Il giorno mar, 01-02-2005 alle 09:14 -0500, Justin Pryzby ha scritto:
> Could you send me or the bug the logfile as an attachment? If that's
> not possible, maybe you can trim the log with a binary search to try
> to narrow down the problem lines as much as possible.
In the attached file you can
On Tue, Feb 01, 2005 at 09:40:46AM +0100, EndelWar wrote:
> Package: sarg
> Version: 2.0.2-1
> Severity: grave
> Justification: renders package unusable
>
> Running sarg on 2 different server cause it to hang up and uses nearly all
> cpu time.
> The command line used is "sarg -l /var/log/squid/ac
Package: sarg
Version: 2.0.2-1
Severity: grave
Justification: renders package unusable
Running sarg on 2 different server cause it to hang up and uses nearly all cpu
time.
The command line used is "sarg -l /var/log/squid/access.log", the log file come
from squid 2.5.7-5 using squidguard 1.2.0-5
5 matches
Mail list logo
