Changes between Initial Version and Version 2 of Ticket #6938


Ignore:
Timestamp:
Sep 22, 2012, 9:44:57 AM (7 years ago)
Author:
arma
Comment:

This happens because Tor puts out that warning while parsing its config, and part of parsing the config is learning what logs the user wants to use. So, there aren't any log files open at that point.

Should we queue "logged stuff" until the log is open, then spit it all out there? That sounds like it could be confusing in the other direction.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #6938

    • Property Component changed from - Select a component to Tor Client
  • Ticket #6938 – Description

    initial v2  
    11Issue:
    2 When configuring Tor as a bridge and to advertise an ORPort, the resulting warning is displayed on the console, but is not logged to the Tor log file.
     2When configuring Tor as a bridge and to advertise a DirPort, the resulting warning is displayed on the console, but is not logged to the Tor log file.
    33
    44Environment: