Hi,
Oskar Pearson wrote:
> Right way: Allow a browser to make changes by interfacing directly with
> squid, using 'PUT cache_object://' or something...
Yup, seems good if this can be coupled with the smart reconfig.
> Other way (not really wrong, see): run a seperate process which listens
> to a different port, and reads and writes the config file. You make changes,
> then say 'restart'. The 'configd' writes the new config file and sends
> a kill -HUP to the squid process...
Which we want to avoid, anyway.
>
> Anotherway (might be a good idea anyway): split the common functions, such
> as ACL's into a seperate file, which you can reload without closing all
> connections....
I'd also like to identify other functions that would permit reconfiguration
without restarting.
How about the ability to PUT sections of the config file?
-- Miguel A.L. Paraz +63-2-750-2288 IPhil Communications, Makati City, Philippines http://www.iphil.netReceived on Tue Jul 29 2003 - 13:15:43 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:11:25 MST