From: Christoph Weber-Fahr on
Henri Hennebert wrote:
> Christoph Weber-Fahr wrote:

>> web1# [~] portaudit -Fad
>> auditfile.tbz 100% of 49 kB 930 kBps
>> portaudit: Database too old.
>> Old database restored.
>
> I encounter the same problem if I use a proxy (squid 3.0)
> eg:
> portaudit_fetch_env="HTTP_PROXY=http://proxy.restart.bel:3128/
> in /usr/local/etc/portaudit.conf
>
> or HTTP_PROXY is defined in the environment (/etc/profile for example)

Yep. My system also uses a proxy.

But since it uses fetch in both cases, that shouldn't make a difference,
should it?

Regards

Christoph Weber-Fahr
From: Henri Hennebert on
Christoph Weber-Fahr wrote:
> Henri Hennebert wrote:
>> Christoph Weber-Fahr wrote:
>
>>> web1# [~] portaudit -Fad
>>> auditfile.tbz 100% of 49 kB 930 kBps
>>> portaudit: Database too old.
>>> Old database restored.
>>
>> I encounter the same problem if I use a proxy (squid 3.0)
>> eg:
>> portaudit_fetch_env="HTTP_PROXY=http://proxy.restart.bel:3128/
>> in /usr/local/etc/portaudit.conf
>>
>> or HTTP_PROXY is defined in the environment (/etc/profile for example)
>
> Yep. My system also uses a proxy.
>
> But since it uses fetch in both cases, that shouldn't make a difference,
> should it?
Obviously, the proxy don't querry the last modification time of the file
and deliver a local copy.

I make some test and was surprise by this behavior. IIRC this problem
appear for me after an upgrade to squid 3.0.

Henri
>
> Regards
>
> Christoph Weber-Fahr