capture tor log messages before control connection is opened
|Reported by:||mcs||Owned by:||nickm|
|Component:||Core Tor/Tor||Version:||Tor: unspecified|
|Severity:||Normal||Keywords:||tbb-usability, extdev-interview, tor-03-unspecified-201612, tbb-wants|
|Cc:||brade, mikeperry, atagar, karsten, asn, catalyst||Actual Points:|
While working on ticket #9675, Kathy Brade and I discovered that the tor log warnings regarding clock skew are sometimes generated very early as tor starts up. Unfortunately, there is a known problem in Tor Launcher where tor log messages are not captured until Tor Launcher is able to connect to the control port and issue a SETEVENTS command (the Mozilla process control APIs do not provide a way to capture stdout or stderr).
One solution is for tor to provide a way to retrieve old log messages (e.g., a new getinfo command) or otherwise provide a way to capture messages that are generated before a control connection is opened. Another option for this specific scenario would be to modify tor to ensure that clock skew is always reported via the status/bootstrap-phase mechanism.
Change History (21)
comment:14 Changed 4 months ago by nickm
- Keywords tor-03-unspecified-201612 added
- Milestone changed from Tor: 0.3.??? to Tor: unspecified