[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

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

#6938: Bridge DirPort warning not logged to Tor log file
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:
  shamrock               |     Status:  needs_review
         Type:  defect   |  Milestone:  Tor: 0.2.6.x-final
     Priority:  major    |    Version:  Tor: 0.2.4.2-alpha
    Component:  Tor      |   Keywords:  tor-client 026-triaged-1 nickm-
   Resolution:           |  patch
Actual Points:           |  Parent ID:  #10059
       Points:           |
-------------------------+-------------------------------------------------
Changes (by nickm):

 * keywords:  tor-client 026-triaged-1 => tor-client 026-triaged-1 nickm-
               patch
 * status:  new => needs_review
 * milestone:  Tor: 0.2.7.x-final => Tor: 0.2.6.x-final


Comment:

 If somebody does a patch, we could take it as early as 0.2.6.

 The way to do it is like this: on startup, have the log mechanism store
 every logged message in a structure holding the time, the severity, the
 log domain, and ...

 oh heck, I'll just do it.

 (90 minutes later)

 See branch "ticket6938" in my public repository.  It'll help with logfiles
 and syslogs, but controllers that want to see early log messages via
 controller events are still out of luck.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6938#comment:11>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs