hey Ricardo.
GOOD and Thanks!
I have seen this issue before but didn't had much time to handle it.
So now the ldap helper works fine??
If I understand right there is something odd about the helpers code
which forces the admin to use more helpers then it used to be in 2.7 and
3.1.
How about te
Hi Eliezer,
I ended up making some changes on my /etc/init.d/squid to force
pidfiles exclusion on /var/run/squid, because when I restart squid it
does not always kill that files (but it end all processes).
My new packages now have the init.d script with that changes and I
have uploaded them here:
> The latest 3.3 should be okay, although we have some reports of weirdness
> still going on as late as 3.3.4.
>
> Amos
I guess the weirdness is going on then:
Squid Cache: Version 3.3.4
configure options: '--build=x86_64-linux-gnu' '--prefix=/usr'
'--includedir=${prefix}/include' '--mandir=$
Eliezer,
you didnt compiled LDAP_group external acl, see your ./configure line:
'--enable-external-acl-helpers=wbinfo_group,kerberos_ldap_group,AD_group'
My:
--enable-external-acl-helpers="file_userip,LDAP_group,kerberos_ldap_group,session,unix_group,wbinfo_group"
But I will try to rebuild your
Eliezer,
You mean change permissions on /dev/shm? It is already "world writeable"
[root@theroutertwo ~]# ll /dev/shm
total 0
drwxrwxrwt. 2 root root 40 Jun 1 12:16 .
(maybe I am doing the hole shm thing wrong)
Btw I will test your package this morning (it is monday morning here
in Brazil now
Hi,
I have followed the same steps that in the previous case but changing the
Operating System. Tried on:
- Fedora 18
- Kernel 3.6.10
- IPtables 1.4.16
- Squid 3.3.5 with Tproxy
Unfortunately, is the same situation that when I was using Ubuntu. The users
can reach Internet only if Squid is wor
Yes it works.
If you need some SHM thing just change the ownership of the directory.
it will solve most of the problems.
If there is some SPEC expert here I will be happy to get some help to do
this change in the SPEC file instead of doing it manually.
Eliezer
On 6/1/2013 11:50 PM, Ricardo Kle
On 3/06/2013 7:45 p.m., Josef Karliak wrote:
Good morning,
In the syslog squid complains about error with creating IPv6 socket :
2013-06-03T07:00:01.856497+02:00 proxyad1 squid[6189]: commBind:
Cannot bind socket FD 21 to [::1]: (99) Cannot assign requested address
2013-06-03T07:00:01.856969
Sounds familar to me on Suse.
Somehow I was not able to completely disable all IPv6 support on my
openSuSE, too, and had similar effects like you.
Try
./configure --disable-ipv6
to compile squid from source as a workaround.
--
View this message in context:
http://squid-web-proxy-cache.1
Good morning,
In the syslog squid complains about error with creating IPv6 socket :
2013-06-03T07:00:01.856497+02:00 proxyad1 squid[6189]: commBind:
Cannot bind socket FD 21 to [::1]: (99) Cannot assign requested address
2013-06-03T07:00:01.856969+02:00 proxyad1 squid[6189]: commBind:
Cann
sorry for spamming you... desolé de vous avoir spammé
here is the video that should explains the origin of the word "SPAM"
Pour vous consoler : l'origine du mot spam viendrait d'ici ( merci Luc)
http://www.youtube.com/watch?v=anwy2MPT5RE&feature=youtube_gdata_player
Alex
11 matches
Mail list logo
