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 syslog (which can also forward them to a remote server) because cache_log format does not support isolating mixed-in access_log records well. HTH, Alex. > -----Original Message----- > From: Alex Rousskov <rousskov@xxxxxxxxxxxxxxxxxxxxxxx> > Sent: 07 September 2021 14:08 > To: Graham Wharton <graham@xxxxxxxxxxxxxx>; squid-users@xxxxxxxxxxxxxxxxxxxxx > Subject: Re: Squid inside docker > > On 9/7/21 8:57 AM, Graham Wharton wrote: >> It would be great if something could be done to help squid running >> inside docker, Particularly > >> 1. Logging to stdout/stderr > > stderr logging is already supported: "squid -d1 ...". > > FWIW, there is also syslog which, when enabled, gets level-0/1 messages: > "squid -s ...". > > >> 2. bash-5.1# squid -k reconfigure >> >> 2021/09/07 13:55:50| FATAL: Bad PID file (/var/run/squid.pid) contains >> unreasonably small PID value: 1 > > Already fixed in master/v6 (commit 3db00ca). The one-character fix is trivial to port to any modern Squid version. > > > HTH, > > Alex. > _______________________________________________ > squid-users mailing list > squid-users@xxxxxxxxxxxxxxxxxxxxx > http://lists.squid-cache.org/listinfo/squid-users > _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
