Re: monitor* feature from 2.6

On Tue, 2008-07-08 at 12:06 +0200, Henrik Nordstrom wrote:
> On tis, 2008-07-08 at 20:57 +1200, Amos Jeffries wrote:
>
> > So the plan of attack appears to be; copy the missing peer_*.* files
> > as-is to 3-HEAD and then locate what the API are and how its being used
> > in 2.x for same usage in 3.x?
>
> Sounds good. Should be trivial to port over (the reasons why these were
> not included in the initial squid-3 port is not technical)

I know this is an old thread, but if somebody is going to work on this,
please add some logic/options that would allow the peer to stay "up"
after N sequential failures. The current Squid2 monitoring code is not
usable in busy environments with occasional isolated failures between
essential peers.

Thank you,

Alex.
Received on Sun Oct 19 2008 - 20:09:47 MDT