On 11/05/2013 2:43 a.m., cac...@quantum-sci.com wrote:
Ah yes, the logrotate path was wrong. Fixed it now.
On Friday, May 10, 2013 07:06:00 AM Helmut Hullen wrote:
What tells
squid -v
about "sysconfdir" (where "squid.conf" is found) and about "with-
logdir"?
--sysconfdir=/etc/squi
Hallo, Cacook,
Du meintest am 10.05.13:
>> What tells
>>
>> grep log /squid.conf
>>
>> about the logging directives?
> The only line uncommented:
> logfile_rotate 2
And nothing like
access_log stdio:/var/log/squid3/access.log
Strange.
> Hm, it appears that squid has built-in
Ah yes, the logrotate path was wrong. Fixed it now.
On Friday, May 10, 2013 07:06:00 AM Helmut Hullen wrote:
> What tells
>
> squid -v
>
> about "sysconfdir" (where "squid.conf" is found) and about "with-
> logdir"?
--sysconfdir=/etc/squid3
--with-logdir=/var/log/squid3
> What tel
Hallo, Cacook,
Du meintest am 10.05.13:
>> If you like we'd probably get that sorted. I'm thinking its a
>> permissions issue in the logs directory, overflowing logs due to log
>> rotation errors (ALL,3 can output a lot of data and get into a bit
>> of trouble getting past 2 or 4 GB).
> OK I've
On 11/05/2013 1:34 a.m., cac...@quantum-sci.com wrote:
On Friday, May 10, 2013 06:17:10 AM Amos Jeffries wrote:
If you like we'd probably get that sorted. I'm thinking its a
permissions issue in the logs directory, overflowing logs due to log
rotation errors (ALL,3 can output a lot of data and g
On Friday, May 10, 2013 06:17:10 AM Amos Jeffries wrote:
> If you like we'd probably get that sorted. I'm thinking its a
> permissions issue in the logs directory, overflowing logs due to log
> rotation errors (ALL,3 can output a lot of data and get into a bit of
> trouble getting past 2 or 4 GB
On 11/05/2013 12:58 a.m., cac...@quantum-sci.com wrote:
On Thursday, May 09, 2013 09:18:53 PM Amos Jeffries wrote:
On 10/05/2013 2:24 a.m., cac...@quantum-sci.com wrote:
OK I guess I have to ditch Squid. I can't live with this.
Well, if you cant or dont want to supply the information needed
On Thursday, May 09, 2013 09:18:53 PM Amos Jeffries wrote:
> On 10/05/2013 2:24 a.m., cac...@quantum-sci.com wrote:
> > OK I guess I have to ditch Squid. I can't live with this.
> >
>
> Well, if you cant or dont want to supply the information needed to help
> there is very little help possible.
On 10/05/2013 2:24 a.m., cac...@quantum-sci.com wrote:
OK I guess I have to ditch Squid. I can't live with this.
Well, if you cant or dont want to supply the information needed to help
there is very little help possible.
On Tuesday, May 07, 2013 09:47:29 PM CACook wrote:
On Tuesday, May
OK I guess I have to ditch Squid. I can't live with this.
On Tuesday, May 07, 2013 09:47:29 PM cac...@quantum-sci.com wrote:
>
> On Tuesday, May 07, 2013 07:04:54 PM Amos Jeffries wrote:
> > What Squid version were you upgrading from?
>
> I didn't notice what version it was before.
>
> >
On Tuesday, May 07, 2013 07:04:54 PM Amos Jeffries wrote:
> What Squid version were you upgrading from?
I didn't notice what version it was before.
> What user-agent / browser software are you using?
Tor Browser, which is Firefox long-term release. I switch between Squid and
Tor with
On 8/05/2013 4:36 a.m., cac...@quantum-sci.com wrote:
Squid 3.3.3-2 on Debian Testing. Suddenly today after a dist-upgrade
yesterday, I am getting a plague of:
Content Encoding Error
The page you are trying to view cannot be shown because it uses an
invalid or unsupported form o
Squid 3.3.3-2 on Debian Testing. Suddenly today after a dist-upgrade
yesterday, I am getting a plague of:
Content Encoding Error
The page you are trying to view cannot be shown because it uses an
invalid or unsupported form of compression.
This is intolerable. Does anyone know th
13 matches
Mail list logo