#28731: log bootstrap tag name for easier troubleshooting -------------------------------------------------+------------------------- Reporter: catalyst | Owner: | catalyst Type: defect | Status: | merge_ready Priority: Medium | Milestone: Tor: | 0.3.5.x-final Component: Core Tor/Tor | Version: Severity: Normal | Resolution: Keywords: s8-bootstrap, 033-backport-maybe, | Actual Points: 034-backport-maybe, 035-backport-maybe | Parent ID: #28018 | Points: 0.1 Reviewer: | Sponsor: | Sponsor8-can -------------------------------------------------+-------------------------
Comment (by nickm): So here's my tentative opinion: 1. Log messages are not intended to be machine readable, and parsing them is always asking for something to break. 2. If you find yourself having to parse a log message, then we are missing some kind of feature to provide the information in some other way, so that you don't have to parse the log message. So the bug might be ours -- we should not assume that applications doing this are being wrong, but rather that we are forcing them to be risky. 3. We could make status events available even earlier, via the OwningControllerFd interface. We might want to have a new option that sets the initial events (like SETEVENTS) on the OwningControllerFd, if that would help. 4. If there is not one already, there should be a GETINFO command that returns the current bootstrap status, so that you don't need to see all the previous bootstrap messages to learn how bootstrapped Tor is. None of these feel like blockers to me, though. If folks don't disagree too strongly, I'll have a look at this code and probably merge it. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28731#comment:8> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs