> > I see that on squid startup, is takes some time while squid rebuilds > > its storage and validates entries in it. > > > > What does that mean, what operations is squid doing in that time?
On 26.11 16:05, Elsen Marc wrote: > - Guess like kind of 'fsck-ing' the store ; watching out > for duplicate url's. Purging such cased e.d. > > Doesn't that make responses somewhat slower? > > As it involves io and store access is locked (swap_fail_miss), probably. > > I have a "farm" of 3 squid caches, hidden behind L3 switch, so I have > > one IP that users connect to. If the squid is slower while rebuilding > > and validating its storage, it is possible without any harm to > > configure squid to do both actions first, and start serving requests > > later. > % squid -h > ... > -F Don't serve any requests until store is rebuilt > ... Ah, this sems to be even worse than original solution - in this case squid accepts connections, but doesn't answer any requests until the store is rebuilt. maybe it should not call accept() before the store rebuild (and probably validation) is done. I understand that why does it bind()/listen() - rebuilding store and then finding out that it can't bind to interfaces would be unwelcome by admins. -- Matus UHLAR - fantomas, [EMAIL PROTECTED] ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. On the other hand, you have different fingers.
