messages out of order in the tor log due to stored logs
Oct 12 04:53:01.000 [notice] Tor 0.2.7.6 opening new log file. Oct 12 04:53:00.963 [warn] OpenSSL version from headers does not match the version we're running with. If you get weird crashes, that might be why. (Compiled with 1000205f: OpenSSL 1.0.2e 3 Dec 2015; running with 1000208f: OpenSSL 1.0.2h 3 May 2016). Oct 12 04:53:00.995 [notice] Tor v0.2.7.6 running on Darwin with Libevent 2.0.22-stable, OpenSSL 1.0.2h and Zlib 1.2.5. Oct 12 04:53:00.995 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Oct 12 04:53:00.995 [notice] Configuration file "/non-existant" not present, using reasonable defaults. Oct 12 04:53:00.999 [notice] Opening Socks listener on 127.0.0.1:16025 Oct 12 04:53:00.999 [notice] Opening Control listener on 127.0.0.1:4367 Oct 12 04:53:01.000 [notice] Parsing GEOIP IPv4 file /usr/local/Cellar/tor/0.2.7.6/share/tor/geoip. Oct 12 04:53:01.000 [notice] Parsing GEOIP IPv6 file /usr/local/Cellar/tor/0.2.7.6/share/tor/geoip6. Oct 12 04:53:02.000 [notice] Bootstrapped 0%: Starting
I looked at
log_prefix_() and, seems, this is NOT a bug in rounding. But maybe I'm wrong. Karsten, please, tell me if you need more logs like that to understand the issue better. Maybe it's really just OS clocks ticking backwards during the test, so feel free to close if you don't consider alike logs interesting.