Willy Tarreau b0b37bcd65 [MEDIUM] further improve monotonic clock by check forward jumps ... The first implementation of the monotonic clock did not verify forward jumps. The consequence is that a fast changing time may expire a lot of tasks. While it does seem minor, in fact it is problematic because most machines which boot with a wrong date are in the past and suddenly see their time jump by several years in the future. The solution is to check if we spent more apparent time in a poller than allowed (with a margin applied). The margin is currently set to 1000 ms. It should be large enough for any poll() to complete. Tests with randomly jumping clock show that the result is quite accurate (error less than 1 second at every change of more than one second).		2008-06-23 14:00:57 +02:00
..
common	[MEDIUM] further improve monotonic clock by check forward jumps	2008-06-23 14:00:57 +02:00
import	[MAJOR] migrated task, tree64 and session to pool2	2007-05-13 19:43:47 +02:00
proto	[BUG] fix the dequeuing logic to ensure that all requests get served	2008-06-20 15:08:06 +02:00
types	[MEDIUM] implement a monotonic internal clock	2008-06-22 17:18:02 +02:00