clock jump error persists into 0.2.0.25-rc

[Scott Bennett]

     I compiled and installed 0.2.0.25-rc to try it out, and I'm sad to write,
it still has the "clock jump" problem and isn't usable:

Apr 24 06:22:18.784 [notice] Tor 0.2.0.25-rc (r14442) opening log file.
Apr 24 06:22:18.785 [warn] Can't log to stdout with RunAsDaemon set; skipping stdout
Apr 24 06:22:18.990 [notice] Your Tor server's identity key fingerprint is 'MYCROFTsOtherChild 0232 2050 5A55 0D6F DF0C 20FF 7C48 E66B A06A 49A6'
Apr 24 06:22:19.432 [notice] This version of Tor (0.2.0.25-rc) is newer than any recommended version, according to the directory authorities. Recommended versions are: 0.1.2.19,0.2.0.23-rc,0.2.0.24-rc
Apr 24 06:22:26.870 [notice] We now have enough directory information to build circuits.
Apr 24 06:22:27.146 [warn] Nickname list includes 'yourd0f670b45a' which isn't a known router.
Apr 24 06:22:27.470 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Apr 24 06:22:29.204 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Apr 24 06:23:29.394 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent.
Apr 24 06:23:47.488 [notice] Performing bandwidth self-test...done.
Apr 24 06:43:39.007 [notice] Tried for 166 seconds to get a connection to [scrubbed]:80. Giving up.
Apr 24 06:43:39.007 [notice] Tried for 166 seconds to get a connection to [scrubbed]:80. Giving up.
Apr 24 06:43:39.007 [notice] Tried for 166 seconds to get a connection to [scrubbed]:80. Giving up.
Apr 24 06:44:05.625 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Apr 24 06:44:05.625 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Apr 24 06:44:06.627 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Apr 24 06:49:24.328 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'kefiroid'. Retrying on a new circuit.
Apr 24 09:31:01.405 [warn] Your system clock just jumped 209 seconds forward; assuming established circuits no longer work.
Apr 24 09:37:12.059 [warn] Your system clock just jumped 117 seconds forward; assuming established circuits no longer work.
Apr 24 09:39:58.548 [warn] Your system clock just jumped 166 seconds forward; assuming established circuits no longer work.
Apr 24 09:42:16.878 [warn] Your system clock just jumped 138 seconds forward; assuming established circuits no longer work.
Apr 24 10:10:46.336 [warn] Your system clock just jumped 153 seconds forward; assuming established circuits no longer work.
Apr 24 10:14:54.156 [warn] Your system clock just jumped 165 seconds forward; assuming established circuits no longer work.
Apr 24 10:17:51.218 [warn] Your system clock just jumped 177 seconds forward; assuming established circuits no longer work.
Apr 24 10:19:35.515 [warn] Your system clock just jumped 104 seconds forward; assuming established circuits no longer work.
Apr 24 10:21:30.414 [warn] Your system clock just jumped 115 seconds forward; assuming established circuits no longer work.
Apr 24 10:23:17.673 [warn] Your system clock just jumped 107 seconds forward; assuming established circuits no longer work.
Apr 24 10:28:57.722 [warn] Your system clock just jumped 252 seconds forward; assuming established circuits no longer work.
Apr 24 10:35:04.234 [warn] Your system clock just jumped 213 seconds forward; assuming established circuits no longer work.
Apr 24 10:48:27.177 [warn] Your system clock just jumped 100 seconds forward; assuming established circuits no longer work.
Apr 24 11:30:51.929 [warn] Your system clock just jumped 133 seconds forward; assuming established circuits no longer work.

At the moment, I'm waiting for it to shutdown, so I can revert once again to
0.2.0.19-alpha, the last release that didn't have the clock jump problem.
Sigh.

Apr 24 14:28:06.232 [notice] Interrupt: will shut down in 1500 seconds. Interrupt again to exit now.
Apr 24 14:31:00.686 [warn] Your system clock just jumped 146 seconds forward; assuming established circuits no longer work.


                                  Scott Bennett, Comm. ASMELG, CFIAG
**********************************************************************
* Internet:       bennett at cs.niu.edu                              *
*--------------------------------------------------------------------*
* "A well regulated and disciplined militia, is at all times a good  *
* objection to the introduction of that bane of all free governments *
* -- a standing army."                                               *
*    -- Gov. John Hancock, New York Journal, 28 January 1790         *
**********************************************************************