Re: R: monitoring squid environment data sources
lör 2009-10-03 klockan 21:19 +0200 skrev Kinkie: > I could not find it... > If it's a dupe, I apologize Well most discussions were before we had a Features section in the wiki...
Re: R: monitoring squid environment data sources
I could not find it... If it's a dupe, I apologize On Saturday, October 3, 2009, Henrik Nordstrom wrote: > ons 2009-09-30 klockan 16:57 +0200 skrev Kinkie: >> On Wed, Sep 30, 2009 at 2:00 PM, Henrik Nordstrom >> wrote: >> > Been thinking a little further on this, and came to the conclusion that >> > effort is better spent on replacing the signal based -k interface with >> > something workable, enabling a control channel into the running Squid to >> > take certain actions. > >> This warrants a Features/ wiki page IMO > > Hmm.. sure it wasn't there already? It's a feature which has been > discussed for a decade or so.. > > Regards > Henrik > > -- /kinkie
Re: R: monitoring squid environment data sources
ons 2009-09-30 klockan 16:57 +0200 skrev Kinkie: > On Wed, Sep 30, 2009 at 2:00 PM, Henrik Nordstrom > wrote: > > Been thinking a little further on this, and came to the conclusion that > > effort is better spent on replacing the signal based -k interface with > > something workable, enabling a control channel into the running Squid to > > take certain actions. > This warrants a Features/ wiki page IMO Hmm.. sure it wasn't there already? It's a feature which has been discussed for a decade or so.. Regards Henrik
Re: R: monitoring squid environment data sources
http://wiki.squid-cache.org/Features/ControlChannel On Wed, Sep 30, 2009 at 4:57 PM, Kinkie wrote: > On Wed, Sep 30, 2009 at 2:00 PM, Henrik Nordstrom > wrote: >> Been thinking a little further on this, and came to the conclusion that >> effort is better spent on replacing the signal based -k interface with >> something workable, enabling a control channel into the running Squid to >> take certain actions. >> >> At least on Linux many of the monitors needed is easier implemented >> externally, just telling Squid what to do when needed. > > This warrants a Features/ wiki page IMO > > -- > /kinkie > -- /kinkie
Re: R: monitoring squid environment data sources
On Wed, Sep 30, 2009 at 2:00 PM, Henrik Nordstrom wrote: > Been thinking a little further on this, and came to the conclusion that > effort is better spent on replacing the signal based -k interface with > something workable, enabling a control channel into the running Squid to > take certain actions. > > At least on Linux many of the monitors needed is easier implemented > externally, just telling Squid what to do when needed. This warrants a Features/ wiki page IMO -- /kinkie
Re: R: monitoring squid environment data sources
Been thinking a little further on this, and came to the conclusion that effort is better spent on replacing the signal based -k interface with something workable, enabling a control channel into the running Squid to take certain actions. At least on Linux many of the monitors needed is easier implemented externally, just telling Squid what to do when needed. Regards Henrik
R: monitoring squid environment data sources
Hi Amos, > > I've been considering the growing number of requests from people needing > squid to monitor various configuration and environment stuff and thinking > about way to do it nicely. > > It seems to me that the master process might be assigned to monitor the > upstate of the child process and additionally set a watch on > filemtime/filectime of: > > resolv.conf > hosts file > squid.conf and all include'd files. > helper binaries/scripts > local host IPs (bit tricky on non-windows as this may block)? > other stuff? > > Generating a reconfigure signal to the child if any of the above have > changes noted since last monitor cycle. > > Controlled by the presence (on) or absence (off) of command line option -M > so that we can know whether to set or not set watch events on config files > before loading squid.conf. > > Maybe optional squid.conf settings to turn off individual monitors if we > really need to monitor some but not others. > > We already monitor the IP address for windows controlled via a squid.conf > setting. Guido would that mechanism be workable from a command line option > instead? > > Ideas comments? > The IP monitor on Windows is very simple because is based on System calls: it's just a sleeping thread registered into Windows network API. Yes, it could be controlled from everywhere :-) Currently the only restriction is that the Squid Windows services must be restarted to enable/disable IP monitoring. Some proposal about monitoring: 1) I think that squid.conf settings to turn off individual monitors are very useful, because not all monitor are needed on all platforms (i.e. : there is no resolv.conf on native Windows, registry is used instead). 2) We should also have for the new squid.conf monitoring settings the capability of different platform dependent default values. I agree with Henrik about the monitors placement. Regards Guido Guido Serassio Acme Consulting S.r.l. Microsoft Gold Certified Partner Via Lucia Savarino, 110098 - Rivoli (TO) - ITALY Tel. : +39.011.9530135 Fax. : +39.011.9781115 Email: guido.seras...@acmeconsulting.it WWW: http://www.acmeconsulting.it
