[Varnish] #623: Should use TIM_mono rather than TIM_real in most places
Varnish
varnish-bugs at projects.linpro.no
Fri Jan 22 09:23:03 CET 2010
#623: Should use TIM_mono rather than TIM_real in most places
----------------------+-----------------------------------------------------
Reporter: slink | Owner: phk
Type: defect | Status: closed
Priority: normal | Milestone: Later
Component: varnishd | Version: trunk
Severity: normal | Resolution: wontfix
Keywords: |
----------------------+-----------------------------------------------------
Changes (by phk):
* status: new => closed
* resolution: => wontfix
Comment:
I originally created TIM_mono() for exactly that purpose, but have since
realized that varnish is so royally screwed that there is no beginning or
end, if the clock is changed in any significant way, because most cache
content is handled on an absolute UTC timescale.
If anything, I think we need to restart the worker thread if we detect a
time-step, because we may have to resort our hash, and the code complexity
for that is certainly not warranted, just for people who cannot get
/etc/ntp.conf right.
So I think the answer is "thanks, but no thanks", this is a problem that
needs to be solved outside Varnish.
Poul-Henning
--
Ticket URL: <http://varnish.projects.linpro.no/ticket/623#comment:1>
Varnish <http://varnish.projects.linpro.no/>
The Varnish HTTP Accelerator
More information about the varnish-bugs
mailing list