n only one
webserver, at some point no clients will find anything at all.
Well, there's a lot of ways of doing the same thing, including ucarp,
squid cache_peer as Amos said... It's just a matter of picking the one
that fits.
On Tue, Nov 18, 2014 at 3:31 AM, Jason Haar wrote:
> On
webserver serve the pac
file and let the DNS balance the requests for the name
"http://wpad.your.domain/wpad.dat";.
On Mon, Nov 17, 2014 at 6:36 PM, Amos Jeffries wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 18/11/2014 12:39 a.m., Carlos Defoe wrote:
>&g
Use a load balancer. HAproxy will do the trick, if you don't want to
spend some money on a professional load balancer like F5 big-ip.
Don't drop the use of wpad. You can send the balancer name (eg.
proxy.your.domain) as a default for every client, and send the names
of the proxy nodes as a failove
Windows 7 inside the domain?
Anyway, you should configure a basic auth scheme as a second fallback.
On Fri, Oct 24, 2014 at 9:26 PM, Markus Moeller
wrote:
> Hi Pedro,
>
> How did you create your keytab ? What does klist –ekt show
> ( I assume you use MIT Kerberos) ?
>
> Markus
>
> "Pedro
no, rhel 6
On Thu, Oct 23, 2014 at 9:51 AM, Eugene M. Zheganin wrote:
> Hi.
>
> On 23.10.2014 18:13, Carlos Defoe wrote:
>> I had this kind of 100% CPU problem with auth helpers when upgrading
>> to squid 3.4. I use negotiate_wrapper, kerberos, ntlm and basic auth.
>>
I had this kind of 100% CPU problem with auth helpers when upgrading
to squid 3.4. I use negotiate_wrapper, kerberos, ntlm and basic auth.
Then I had to fall back to 3.3 and it is production until now, with
some troubles with broken clients, but with normal cpu usage most of
the time.
Can you try w
