search for: dns_nameserv

It''s now been over a week, and we are nearly at wits end trying to track down our performance issues here. We now have a P3/667 (single CPU! SMP was definitely the source of previous lockups) with 256Mb RAM. It is running along with a load avg of less than 0.1 even at peak times. Max ip_conntrack is around 1500-2000. Sounds fine, but, we have also tried 3 different squid proxies (2

Hi. I use winbind + squid on Debian Buster to authenticate users + authorize them based on groups they are in. It all works, well, good, but winbind's CPU utilization peaks can reach up to 100%. The same solution ran OK on Debian Jessie with up to 20% CPU utilization at most. The configuration of Buster must have been updated based on the samba version leap/shift compared to Jessie. On

..._mgr admin at localhostaccess_log /var/squid/logs/access.logcache_log /var/squid/logs/cache.logreferer_log /var/squid/logs/referer.loglogfile_rotate 0cache_store_log noneshutdown_lifetime 3 seconds# Allow local network(s) on interface(s)acl localnet src 192.168.0.0/255.255.255.0uri_whitespace stripdns_nameservers 208.67.222.222cache_mem 8 MBmaximum_object_size_in_memory 32 KBmemory_replacement_policy heap GDSFcache_replacement_policy heap LFUDAcache_dir ufs /var/squid/cache 100 16 256minimum_object_size 0 KBmaximum_object_size 4 KBoffline_mode offcache_swap_low 90cache_swap_high 95 url_rewrite_program /u...