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

Re: [tor-bugs] #21542 [Applications/Tor Launcher]: use Subprocess.jsm to launch tor



#21542: use Subprocess.jsm to launch tor
---------------------------------------+-----------------------
 Reporter:  mcs                        |          Owner:  brade
     Type:  defect                     |         Status:  new
 Priority:  Medium                     |      Milestone:
Component:  Applications/Tor Launcher  |        Version:
 Severity:  Normal                     |     Resolution:
 Keywords:  tbb-usability, ff52-esr    |  Actual Points:
Parent ID:  #10059                     |         Points:
 Reviewer:                             |        Sponsor:
---------------------------------------+-----------------------

Comment (by mcs):

 Replying to [comment:4 arma]:
 > Sounds plausible!
 >
 > Right now Tor has a hard-coded log to stdout that it adds during
 startup, but we could -- hm. I was going to say we could make it
 configurable, but that won't work. I guess Tor Browser could patch Tor
 before building it, to make that stdout into a stderr?

 Firefox's Subprocess.jsm allows access to both stdout and stderr, so I
 don't think the network team needs to make any changes. I just assumed the
 log was being sent to stderr. Is anything sent to stderr?

 Obviously the advantage of this approach (capture tor's stdout) over the
 one described in ticket:10059#comment:17 is that in most cases
 '''something''' will be logged to stdout even if tor never gets to the
 point of opening a control port listener.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21542#comment:5>
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