Hi all,
I made a little progress on this.
If you run squid as root, it forks and assumes the identity of the
cache_effective_user. When it does this, it is denied access to stdout.
If you run squid as user squid (or whoever your cache_effective_user), it does
not change user, and the squid use
On 9/09/21 3:55 am, Graham Wharton wrote:
If you run squid as user squid (or whoever your cache_effective_user), it does
not change user, and the squid user has full access to write to stdout, so
...
2021-09-08T16:49:15.065+01:00 2021/09/08 16:49:15| WARNING: no_suid:
setuid(0): (1) Opera
Are you aware of any options to direct the access log to stdout aswell as the
cache log?
-Original Message-
From: Alex Rousskov
Sent: 07 September 2021 14:08
To: Graham Wharton ; squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Squid inside docker
On 9/7/21 8:57 AM, Graham
On 9/8/21 8:06 AM, Graham Wharton wrote:
> Are you aware of any options to direct the access log to stdout
> aswell as the cache log?
I suspect it is possible to hack it, but I think it is better to send
access log records to a dedicated TCP server (which can probably be as
simple as netcat) or s
This hack only works if you are building manually from source code, in
the same directory you expanded the sources. Which is not he case for
anyone building with automated tools or CI systems.
The earlier provided ./configure parameter change works just as well
without manual changes to the so
>
> cp ../../src/tests/stub_debug.cc tests/stub_debug.cc
> cp: cannot create regular file 'tests/stub_debug.cc': No such file or
> directory
> make[3]: *** [Makefile:1489: tests/stub_debug.cc] Error 1
> make[3]: Leaving directory '/home/ingo/Downloads/squid-5.1/tools/squidclient'
> make[2]: *** [M
