[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #10059 [Tor]: capture tor log messages before control connection is opened
#10059: capture tor log messages before control connection is opened
---------------------------------------------+-----------------------------
Reporter: mcs | Owner: nickm
Type: defect | Status: new
Priority: Medium | Milestone: Tor:
Component: Tor | 0.2.???
Severity: Normal | Version: Tor:
Keywords: tbb-usability, extdev-interview | unspecified
Parent ID: #9675 | Resolution:
Sponsor: | Actual Points:
| Points:
---------------------------------------------+-----------------------------
Changes (by mcs):
* severity: => Normal
Comment:
Replying to [comment:9 nickm]:
> I'm okay with doing an in-tor solution for this if you decide one is
necessary; just let me know. It would probably involve adding a log type
that lets you store the last N kb of log messages in a queue, and later
query them via the control port.
(I am revisiting some old tickets today.) For Tor Launcher, it would be
convenient to have a mechanism in tor such as the one you described. One
tricky thing is that we would want to be sure Tor Launcher receives the
entire, correct stream of messages (without duplicates or gaps), so we
would need to figure out how to merge the queued messages with the ones we
receive in response to SETEVENTS NOTICE WARN ERR. I am not sure how to do
that unless tor assigns a sequence number or something similar to each
message. Or it might work for tor to provide an option to send the queued
messages as events as soon as the SETEVENTS command is received.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10059#comment:12>
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