Re: odd warning at shutdown

[Scott Bennett <bennett@xxxxxxxxxx>]

     Looks like 0.2.1.2-alpha also gives the weird message before shutting
down.  After starting it the first two times, I had to shut it down almost
immediately in order to shut the system down again.  Here are the log file
entries from the second shutdown.

Jul 03 05:51:51.772 [notice] Tor 0.2.1.2-alpha (r15383) opening log file.
Jul 03 05:51:51.794 [warn] Can't log to stdout with RunAsDaemon set; skipping stdout
Jul 03 05:51:52.486 [notice] Your Tor server's identity key fingerprint is 'MYCROFTsOtherChild 0232 2050 5A55 0D6F DF0C 20FF 7C48 E66B A06A 49A6'
Jul 03 05:51:52.486 [notice] Bootstrapped 0%: Starting.
Jul 03 05:51:57.137 [notice] We now have enough directory information to build circuits.
Jul 03 05:51:57.137 [notice] Bootstrapped 80%: Connecting to the Tor network.
Jul 03 05:51:57.964 [warn] Nickname list includes 'yourd0f670b45a' which isn't a known router.
Jul 03 05:51:57.984 [notice] Bootstrapped 85%: Finishing handshake with first hop.
Jul 03 05:51:58.377 [notice] Bootstrapped 90%: Establishing a Tor circuit.
Jul 03 05:51:59.563 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Jul 03 05:51:59.563 [notice] Bootstrapped 100%: Done.
Jul 03 05:51:59.563 [notice] Now checking whether ORPort 66.225.36.17:995 and DirPort 66.225.36.17:443 are reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Jul 03 05:52:06.643 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent.
Jul 03 05:52:07.588 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Jul 03 05:52:15.721 [notice] Performing bandwidth self-test...done.
Jul 03 05:52:41.909 [notice] Interrupt: will shut down in 1500 seconds. Interrupt again to exit now.
Jul 03 06:03:25.327 [notice] Sigint received a second time; exiting now.
Jul 03 06:03:25.400 [warn] Still had some address policies cached at shutdown.

					Scott