Re: [squid-users] Squid 3.4.11 crashing on FreeBSD 10 (64-bit)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have just fixed a few clang detected build errors and 3.5 is now building cleanly here on FreeBSD 10 with the default Clang. Please try to build the latest 3.5 snapshot (which will be labeled r13735 or higher). It should build fine with either the system default clang compiler or your GCC 4.9 install, but not with the system default GCC 4.4. (gdb) bt #0 0x000803a30469 in swapcontext () from /lib/libthr.so.3 #1 0x000803a30062 in sigaction () from /lib/libthr.so.3 #2 signal handler called #3 0x000803d6b04a in kevent () from /lib/libc.so.7 #4 0x0086335c in Comm::DoSelect (msec=981) at ModKqueue.cc:264 Looks like a bug in the system threading library. Though why Squid is triggering it is unknown. Maybe related to the two GCC versions with different libc perhapse? Amos -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJUvkdXAAoJELJo5wb/XPRjlvAIAMFp6QV6Dq+IEzUfdrh510F0 u2w/qba0om8a/9V3VnO5H1fHt4uIiHD9Nfph0jqhpkNPP34grO5CFOJRTIRwgni7 9GO2Dq6UKYFz2onkoQlm2Oa/72LEsBupWThL2chlsowztedhObIHAt4qUqLCbTo4 ogwIvf30wFQ4xTYMj1KLmFjbUYM/EIag+c9A67w7RB1kxQqtIHxdwQYrRbjli66s 6D6FYoFZ3BwlulWylNqjB8z98ah0/wn761rcrt2jYmAmM8OvYrezspn5BviAF6YP 1m/skvaEIFP3i3wJZUSY5AoD3EFYAZp0PJL6zXaXKhhERCjZ4/ekiA5rjlqnSZo= =pv6K -END PGP SIGNATURE- ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
Re: [squid-users] Squid 3.4.11 crashing on FreeBSD 10 (64-bit)
On 20 January 2015 at 15:17, Amos Jeffries squ...@treenet.co.nz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have just fixed a few clang detected build errors and 3.5 is now building cleanly here on FreeBSD 10 with the default Clang. Please try to build the latest 3.5 snapshot (which will be labeled r13735 or higher). It should build fine with either the system default clang compiler or your GCC 4.9 install, but not with the system default GCC 4.4. I will check on that. However, I earlier today managed to compile 3.5.0.4 using clang. The problem I have been facing now is about 'forwarding loop detected' over and over... checking on my PF rules hasn't yielded anything. And I am now wondering why 3.4.11 wasn't seeing these forwarding loops.. (gdb) bt #0 0x000803a30469 in swapcontext () from /lib/libthr.so.3 #1 0x000803a30062 in sigaction () from /lib/libthr.so.3 #2 signal handler called #3 0x000803d6b04a in kevent () from /lib/libc.so.7 #4 0x0086335c in Comm::DoSelect (msec=981) at ModKqueue.cc:264 Looks like a bug in the system threading library. Though why Squid is triggering it is unknown. Maybe related to the two GCC versions with different libc perhapse? I only have one gcc version on my system -gcc49 -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 I can't hear you -- I'm using the scrambler. ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
Re: [squid-users] Squid 3.4.11 crashing on FreeBSD 10 (64-bit)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21/01/2015 6:11 a.m., Odhiambo Washington wrote: On 20 January 2015 at 16:16, Odhiambo Washington wrote: 1. I see these in cache.log 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted Not to worry about. An artifact of how Squid runs helpers vs BSD default permissions for fork()ed processes. Squid is just unable to drop root permissions silently (for now) because the OS already did it. 2015/01/20 20:00:18| Logfile: opening log stdio:/usr/local/squid/logs/access.log But then I have no joy because of 2015/01/20 20:03:55| WARNING: Forwarding loop detected for:.. I am almost thinking FreeBSD 9.3 would be better... I haven't seen so much grief. I am beginning to wonder if the PF version may has changed in FreeBSD. In OpenBSD (4.6 IIRC) PF went from a version where rdr-to rules worked to one where only divert-to would work reliably and rdr-to only sometimes. It may be that the changover has finally hit FreeBSD. ADDENDUM: When compiled with --enable-ipf-transparent, it fails to compile as follows: As Yuri said, PF --enable-pf-transparent (no 'I') or IPFW - --enable-ipfw-transparent (note the 'W') for FreeBSD. Amos -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJUvqNzAAoJELJo5wb/XPRjywsH/RY9myLQSx/FaQf6gmWykbd7 /bNXzg0JxoiUar56gYseUk6yEp9YhtSpAFEFnVaen7ee/4xNW7o8Tv7R0gTrcqWy lTUFtuPRyP3EQ7tsYNjLgF2dYYX4Eb1E1zDVCmdUHtvG/d7YTnC9LgLYrNqgF9v6 Bgck0S2aC2Q4vdsn34LsjbgKmtnpqr+47I4Eco5TfyHZvsCHp2EUb0RwgA/hus8E Q0x6Jnmv1idIywsuLXhCbPtsriWXJf38cDtOs6UNFmAo0fr762oBH94i2xXIDb1Y 8qZzOGS09G93qWn027UZmqWHlcH8p3c0fo17LqXekcrBGW2gxd82+ABvbH6JZBk= =tAVB -END PGP SIGNATURE- ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
Re: [squid-users] Squid 3.4.11 crashing on FreeBSD 10 (64-bit)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 20.01.2015 23:11, Odhiambo Washington пишет: On 20 January 2015 at 16:16, Odhiambo Washington odhia...@gmail.com mailto:odhia...@gmail.com wrote: On 20 January 2015 at 15:17, Amos Jeffries squ...@treenet.co.nz mailto:squ...@treenet.co.nz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have just fixed a few clang detected build errors and 3.5 is now building cleanly here on FreeBSD 10 with the default Clang. Please try to build the latest 3.5 snapshot (which will be labeled r13735 or higher). It should build fine with either the system default clang compiler or your GCC 4.9 install, but not with the system default GCC 4.4. I will check on that. However, I earlier today managed to compile 3.5.0.4 using clang. The problem I have been facing now is about 'forwarding loop detected' over and over... checking on my PF rules hasn't yielded anything. And I am now wondering why 3.4.11 wasn't seeing these forwarding loops.. May be, It has another configuration? I.e - has not redirectors, or web-server on another port, or another NAT settings? (gdb) bt #0 0x000803a30469 in swapcontext () from /lib/libthr.so.3 #1 0x000803a30062 in sigaction () from /lib/libthr.so.3 #2 signal handler called #3 0x000803d6b04a in kevent () from /lib/libc.so.7 #4 0x0086335c in Comm::DoSelect (msec=981) at ModKqueue.cc:264 Looks like a bug in the system threading library. Though why Squid is triggering it is unknown. Maybe related to the two GCC versions with different libc perhapse? I only have one gcc version on my system -gcc49 root@mail:/home/wash/ILI/Squid/3.5/squid-3.5.1-20150120-r13736 # /opt/squid35/sbin/squid -v Squid Cache: Version 3.5.1-20150120-r13736 Service Name: squid configure options: '--prefix=/opt/squid35' '--enable-removal-policies=lru heap' '--disable-epoll' '--enable-auth' '--enable-auth-basic=DB NCSA PAM PAM POP3 SSPI' '--enable-external-acl-helpers=session unix_group file_userip' '--enable-auth-negotiate=kerberos' '--with-pthreads' '--enable-storeio=ufs diskd rock aufs' '--enable-delay-pools' '--enable-snmp' '--with-openssl=/usr' '--enable-forw-via-db' '--enable-cache-digests' '--enable-wccpv2' '--enable-follow-x-forwarded-for' '--with-large-files' '--enable-large-cache-files' '--enable-esi' '--enable-kqueue' '--enable-icap-client' '--enable-kill-parent-hack' '--enable-ssl' '--enable-leakfinder' '--enable-ssl-crtd' '--enable-url-rewrite-helpers' '--enable-xmalloc-statistics' '--enable-stacktraces' '--enable-zph-qos' '--enable-eui' '--enable-pf-transparent' 'CC=clang' 'CXX=clang++' --enable-ltdl-convenience 1. I see these in cache.log 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| Logfile: opening log stdio:/usr/local/squid/logs/access.log But then I have no joy because of 2015/01/20 20:03:55| WARNING: Forwarding loop detected for:.. Forwarding loop is squid.conf issue, not squid itself. More often you using one port for proxying and web-server on proxy at the same time. Either NAT or squid/web server/redirector(s) program configuration. I am almost thinking FreeBSD 9.3 would be better... I haven't seen so much grief. ADDENDUM: When compiled with --enable-ipf-transparent, it fails to compile as follows: You have not IP Filter in FreeBSD. Just IPFW and PF. AFAIK today IP Filter is absent in xBSD. root@mail:/home/wash/ILI/Squid/3.5/squid-3.5.1-20150120-r13736 # make Making all in compat depbase=`echo assert.lo | sed 's|[^/]*$|.deps/|;s|\.lo$||'`; /bin/sh ../libtool --tag=CXX--mode=compile clang++ -DHAVE_CONFIG_H-I.. -I../include -I../lib -I../src -I../include
Re: [squid-users] Squid 3.4.11 crashing on FreeBSD 10 (64-bit)
On 20/01/2015 21:39, Odhiambo Washington wrote: I know this. I was just mentioning. I think I believe Yuri that IPFilter isn't in FreeBSD. I think I am going to have to suck it in, because I am happy with it in many servers, working nicely with Squid. Hey, From the FreeBSD handbook a list of firewalls: https://www.freebsd.org/doc/handbook/firewalls.html I was just recently testing couple things with FBSD firewalls and I am curios on how would the firewall(pf,ipfw,others...) rules look like for tproxy and intercept. Thanks, Eliezer ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
Re: [squid-users] Squid 3.4.11 crashing on FreeBSD 10 (64-bit)
Yuri, You need a sane MuA. What you have makes life quite difficult for me reading your responses. And I read from gmail web UI. Just to answer you.. On 20 January 2015 at 21:28, Yuri Voinov yvoi...@gmail.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 20.01.2015 23:11, Odhiambo Washington пишет: On 20 January 2015 at 16:16, Odhiambo Washington odhia...@gmail.com mailto:odhia...@gmail.com odhia...@gmail.com wrote: On 20 January 2015 at 15:17, Amos Jeffries squ...@treenet.co.nz mailto:squ...@treenet.co.nz squ...@treenet.co.nz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have just fixed a few clang detected build errors and 3.5 is now building cleanly here on FreeBSD 10 with the default Clang. Please try to build the latest 3.5 snapshot (which will be labeled r13735 or higher). It should build fine with either the system default clang compiler or your GCC 4.9 install, but not with the system default GCC 4.4. I will check on that. However, I earlier today managed to compile 3.5.0.4 using clang. The problem I have been facing now is about 'forwarding loop detected' over and over... checking on my PF rules hasn't yielded anything. And I am now wondering why 3.4.11 wasn't seeing these forwarding loops.. May be, It has another configuration? I.e - has not redirectors, or web-server on another port, or another NAT settings? (gdb) bt #0 0x000803a30469 in swapcontext () from /lib/libthr.so.3 #1 0x000803a30062 in sigaction () from /lib/libthr.so.3 #2 signal handler called #3 0x000803d6b04a in kevent () from /lib/libc.so.7 #4 0x0086335c in Comm::DoSelect (msec=981) at ModKqueue.cc:264 Looks like a bug in the system threading library. Though why Squid is triggering it is unknown. Maybe related to the two GCC versions with different libc perhapse? I only have one gcc version on my system -gcc49 root@mail:/home/wash/ILI/Squid/3.5/squid-3.5.1-20150120-r13736 # /opt/squid35/sbin/squid -v Squid Cache: Version 3.5.1-20150120-r13736 Service Name: squid configure options: '--prefix=/opt/squid35' '--enable-removal-policies=lru heap' '--disable-epoll' '--enable-auth' '--enable-auth-basic=DB NCSA PAM PAM POP3 SSPI' '--enable-external-acl-helpers=session unix_group file_userip' '--enable-auth-negotiate=kerberos' '--with-pthreads' '--enable-storeio=ufs diskd rock aufs' '--enable-delay-pools' '--enable-snmp' '--with-openssl=/usr' '--enable-forw-via-db' '--enable-cache-digests' '--enable-wccpv2' '--enable-follow-x-forwarded-for' '--with-large-files' '--enable-large-cache-files' '--enable-esi' '--enable-kqueue' '--enable-icap-client' '--enable-kill-parent-hack' '--enable-ssl' '--enable-leakfinder' '--enable-ssl-crtd' '--enable-url-rewrite-helpers' '--enable-xmalloc-statistics' '--enable-stacktraces' '--enable-zph-qos' '--enable-eui' '--enable-pf-transparent' 'CC=clang' 'CXX=clang++' --enable-ltdl-convenience 1. I see these in cache.log 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| WARNING: no_suid: setuid(0): (1) Operation not permitted 2015/01/20 20:00:18| Logfile: opening log stdio:/usr/local/squid/logs/access.log But then I have no joy because of 2015/01/20 20:03:55| WARNING: Forwarding loop detected for:.. Forwarding loop is squid.conf issue, not squid itself. More often you using one port for proxying and web-server on proxy at the same time. Either NAT or squid/web server/redirector(s) program configuration. None of those. I read the HOWTO very well. I use Squid+IPFilter on several FreeBSD servers already. My configs are fine. I run squid on 13128 which is different than what I run
[squid-users] Squid 3.4.11 crashing on FreeBSD 10 (64-bit)
I have installed squid on FreeBSD and it's crashing with errors as seen from http://pastebin.com/yC6YZ7Bg. My squid.conf is seen at http://pastebin.com/hJpPXJ0K I am using the Squid in a tranparent proxy mode with PF firewall. Squid is installed from FreeBSD ports: root@mail:/usr/local/etc/squid # squid -v Squid Cache: Version 3.4.11 configure options: '--with-default-user=squid' '--bindir=/usr/local/sbin' '--sbindir=/usr/local/sbin' '--datadir=/usr/local/etc/squid' '--libexe cdir=/usr/local/libexec/squid' '--localstatedir=/var' '--sysconfdir=/usr/local/etc/squid' '--with-logdir=/var/log/squid' '--with-pidfile=/var/run /squid/squid.pid' '--with-swapdir=/var/squid/cache' '--enable-auth' '--enable-build-info' '--enable-loadable-modules' '--enable-removal-policies= lru heap' '--disable-epoll' '--disable-linux-netfilter' '--disable-linux-tproxy' '--disable-translation' '--disable-arch-native' '--enable-eui' ' --enable-cache-digests' '--enable-delay-pools' '--disable-ecap' '--disable-esi' '--enable-follow-x-forwarded-for' '--enable-htcp' '--enable-icap- client' '--enable-icmp' '--enable-ident-lookups' '--enable-ipv6' '--enable-kqueue' '--with-large-files' '--enable-http-violations' '--enable-snmp ' '--enable-ssl' '--enable-ssl-crtd' '--disable-stacktraces' '--disable-ipf-transparent' '--disable-ipfw-transparent' '--enable-pf-transparent' ' --with-nat-devpf' '--enable-forw-via-db' '--enable-wccp' '--enable-wccpv2' '--enable-auth-basic=DB MSNT MSNT-multi-domain NCSA PAM POP3 RADIUS fa ke getpwnam NIS' '--enable-auth-digest=file' '--enable-external-acl-helpers=file_userip time_quota unix_group SQL_session' '--enable-auth-negotia te=kerberos wrapper' '--enable-auth-ntlm=fake smb_lm' '--enable-storeio=ufs aufs diskd' '--enable-disk-io=AIO Blocking IpcIo Mmapped DiskThreads DiskDaemon' '--enable-log-daemon-helpers=file' '--enable-url-rewrite-helpers=fake' '--enable-storeid-rewrite-helpers=file' '--with-openssl=/usr' '--disable-optimizations' '--enable-debug-cbdata' '--prefix=/usr/local' '--mandir=/usr/local/man' '--infodir=/usr/local/info/' '--build=amd64-por tbld-freebsd10.1' 'build_alias=amd64-portbld-freebsd10.1' 'CC=clang' 'CFLAGS=-pipe -march=native -I/usr/include -g -fstack-protector -fno-strict -aliasing' 'LDFLAGS= -pthread -Wl,-rpath,/usr/lib:/usr/local/lib -L/usr/lib -fstack-protector' 'LIBS=' 'CPPFLAGS=' 'CXX=clang++' 'CXXFLAGS=-pipe -march=native -I/usr/include -g -fstack-protector -fno-strict-aliasing -Wno-unused-private-field' 'CPP=clang-cpp' --enable-ltdl-convenience I appreciate any pointers. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 I can't hear you -- I'm using the scrambler. ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
Re: [squid-users] Squid 3.4.11 crashing on FreeBSD 10 (64-bit)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 20/01/2015 4:20 a.m., Odhiambo Washington wrote: On 19 January 2015 at 17:55, Yuri Voinov wrote: Your use CLang. This is the single point. You can get any effects. Looks like this is not Squid problem. Just system. Are you insinuating that Squid-3.x is not supposed to run on FreeBSD 10 because of the CLANG thing? We build test Squid on Clang for FreeBSD 10 (no longer GCC). So it should build and run fine. (Though our FreeBSD 10 tests are failing on man(8) page creation recently). Your build parameter 'CPP=clang-cpp' seems unusual. We do not use/need that for the integration testing builds. Just CC=clang CXX=clang++. The toolchain naturally takes care of the rest. Only the FreeBSD 9.x have clang build issues from the GCC-clang transitional bugs coming at it from all sides (kernel, compiler, and Squid). Do you have a little howto on how I can compile it using gcc (I have gcc49 installed) ? At the simplest: mkdir _build \ cd _build \ ../configure \ make install The squid default paths etc were all designed for FreeBSD environment. This squid is running, disobeying my time-based ACLs, crashing as seen in cache.log and ... just annoying but I need a proxy by all means! It kinda puts me in the proverbial between a rock hard place. If you are using diskd cache_dir on FreeBSD 10 there are known crashes from that in 9/10. Until that is figured out shifting to ufs or aufs is best. Since it is a crash, backtrace is critical to figuring out what is actually going on. Amos -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJUvSywAAoJELJo5wb/XPRjXzcIALlLN2vv/Ev+l0fibkRwDpab m2RWtxzuwNJ958PO92akm4kkJN/0eZojl1lP7Tp8YPVzuIvcTKQ8z+LfhmV7f6Tp /1KA9vqXE+QtZCbPTl1TRv0ar7bwtMGvD12fs8eeApqshesbm9m/mo7eAHNTqMfE gTTJ5IjsCGimxK5b+zOrseOm3Syf1o757E7/3XB26gRhorzdj8Zjvzj7mt41jR6x PlyJybHp/RTt1meZSQQIMUvXdEAOPSAb1kY+R7KY5jqpFdtN3yijDc25lWdpjCub aY2sv+lf5YNeOXlXO/dBicQRQJ0W9H2V4X5lc/qit3YTuIdJx+DHS8qknBzBqv4= =eiso -END PGP SIGNATURE- ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
