On 20/03/19 2:34 am, Joey Officer wrote: > Confirmed I'm on Squid v4 > > # squid --version > Squid Cache: Version 4.4 > Service Name: squid > > I added the above and restarted my container, but the logged output has no change. I also wanted to add that I may not have provided enough information. The spam log entries are stdout - which is where Cloudwatch (in my case) is logging the events. Squid container is being started with the following command: > > squid -f /etc/squid/squid.conf -NYCd 1 > > which is the following options: > -N Master process runs in foreground and is a worker. No kids. > -Y Only return UDP_HIT or UDP_MISS_NOFETCH during fast reload. > -C Do not catch fatal signals. > -d level Write debugging to stderr also. > > I don't have access to the access.log itself, so I'll have to assume the above entry is working for that file. With that in mind, how would I apply the same filter to the stdout of the squid process? > There is no Squid output on stdout. Your _Cloudwatch_ thing may be sending log data there, but that has nothing directly to do with Squid. At most Squid prints some initial messages to stderr on startup which Unix based OS typically write into a kernel log called '/var/log/messages' (but YMMV). Once the cache.log *file* is initialized critical and important notices, along with all helper stderr outputs go to that cache.log file. ***** Please note that setting cache.log to /dev/null is highly dangerous. Squid log rotation, restart etc may *replace* the filesystem special inode for /dev/null with a regular inode for a cache.log file. Squid has root privileges on startup (required for other device access and actions) which allow that inode replacement to be possible. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
