[tor-bugs] #6938 [Tor Client]: Bridge DirPort warning not logged to Tor log file

[Tor Bug Tracker & Wiki]

#6938: Bridge DirPort warning not logged to Tor log file
------------------------+---------------------------------------------------
 Reporter:  shamrock    |          Owner:                    
     Type:  defect      |         Status:  new               
 Priority:  trivial     |      Milestone:                    
Component:  Tor Client  |        Version:  Tor: 0.2.4.2-alpha
 Keywords:              |         Parent:                    
   Points:              |   Actualpoints:                    
------------------------+---------------------------------------------------
Changes (by arma):

  * component:  - Select a component => Tor Client


Old description:

> Issue:
> 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.
>
> Environment:
> Debian squeeze amd64, latest patches
> Tor version 0.2.4.2-alpha (git-0537dc6364594474)
>
> How to reproduce:
> Set "BridgeRelay 1"
> Set "DirPort 80"
>
> Start Tor.
>
> The following warning will be displayed on the console:
> "Starting tor daemon...<date will be here> [warn] Can't set a DirPort on
> a bridge relay; disabling DirPort
> done."
>
> No corresponding warning is logged to the Tor log file.

New description:

 Issue:
 When 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.

 Environment:
 Debian squeeze amd64, latest patches
 Tor version 0.2.4.2-alpha (git-0537dc6364594474)

 How to reproduce:
 Set "BridgeRelay 1"
 Set "DirPort 80"

 Start Tor.

 The following warning will be displayed on the console:
 "Starting tor daemon...<date will be here> [warn] Can't set a DirPort on a
 bridge relay; disabling DirPort
 done."

 No corresponding warning is logged to the Tor log file.

--

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.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6938#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online