[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #28731 [Core Tor/Tor]: log bootstrap tag name for easier troubleshooting
#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 atagar):
Hi David, I agree with everything you said. Parsing the bootstrap lines is
no bueno but is done anyway because it's the only game in town when the
user hasn't opened a control port.
Quick food for thought: how about a '--bootstrap-status' argument to tor
which, when provided, has tor provide machine parseable messages on
stdout? This would allow the network team to freely update these human
read messages at will, but also provide a formally speced message that
scripts who lack a control port can use as well to get the bootstrapping
status.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28731#comment:7>
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