If you're talking about a http-accelerator, there are a couple of usable workarounds. You could, for instance, have a daemon that constantly pings your target server. If it fails, it immediately updates your refresh_patterns and toggles offline_mode to on. This does require that you've managed to grab a cache of the site at some point though. OTOH; you probably shouldn't be running a http-accelerator across different physical networks if you're not sure about what you're doing. / o -----Original Message----- From: Wennie V. Lagmay [mailto:wlagmay@xxxxxxxxxxxxx] Sent: den 9 april 2006 10:56 To: Mark Elsen Cc: squid users Subject: Re: Squid connection I stand corrected on my wrong assumtion, thanks M. Any way does it means that without touching the Squid server even 24 hours of backbone failure, and the moment the backbone link re-establish, Squid will also re establish automatically? Wennie ----- Original Message ----- From: "Mark Elsen" <mark.elsen@xxxxxxxxx> To: "Wennie V. Lagmay" <wlagmay@xxxxxxxxxxxxx> Cc: "squid users" <squid-users@xxxxxxxxxxxxxxx> Sent: Sunday, April 09, 2006 11:17 AM Subject: Re: Squid connection > I know that if the backbone link fails, squid will still try to connect to > the internet ?? >and if the backbone link re establish squid will automatically > re establish too. My question, how long can Squid waits for the re > establishment of backbone link, that the squid service can tolerate and > will > not shutdown it self automatically. fyi in using Squid-2.5Stable13. > > - Squid will never shutdown when the Internet link is not available, connection attempts will fail however , leading to failing statuses for/from URI's in access.log and lot's of related info in cache.log however. The induced pre-assumption(s) , are therefore simply wrong. M.
