-
Show log
Commit
-
Hash : dfd808cb
Author :
Date : 2012-04-19T00:25:12
If time has jumped so we'd reschedule a periodic event in the past, schedule it for the future instead Fixes an issue reported on libevent-users in the thread "a dead looping bug when changing system time backward". Previously, if time jumped forward 1 hour[*] and we had a one-second periodic timer event, that event would get invoked 3600 times. That's almost certainly not what anybody wants. In a future version of Libevent, we should expose the amount of time that the callbac kwould have been invoked somehow. [*] Forward time jumps can happen with nonmonotonic clocks, or with clocks that jump on suspend/resume. It can also happen from Libevent's point of view if the user exits from event_base_loop() and doesn't call it again for a while.
-
Files
- Makefile.am
- Makefile.nmake
- bench.c
- bench_cascade.c
- bench_http.c
- bench_httpclient.c
- regress.c
- regress.h
- regress.rpc
- regress_buffer.c
- regress_bufferevent.c
- regress_dns.c
- regress_et.c
- regress_http.c
- regress_iocp.c
- regress_listener.c
- regress_main.c
- regress_minheap.c
- regress_rpc.c
- regress_ssl.c
- regress_testutils.c
- regress_testutils.h
- regress_thread.c
- regress_util.c
- regress_zlib.c
- rpcgen_wrapper.sh
- test-changelist.c
- test-eof.c
- test-init.c
- test-ratelim.c
- test-ratelim.sh
- test-time.c
- test-weof.c
- test.sh
- tinytest.c
- tinytest.h
- tinytest_demo.c
- tinytest_local.h
- tinytest_macros.h
-
Properties
