Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #7667

Closed
Open
Opened Dec 08, 2012 by Robert Ransom@rransom

Support launching an ‘owned’ Tor process

#7666 (closed) suggests that Stem provide an easy way to send the TAKEOWNERSHIP command along a control-port connection (and provides a patch). This may be useful (at least within Stem), but it is probably too low-level for controller authors to use correctly.

Instead, Stem should provide an easy way to launch a Tor process which is ‘owned’ by the controller process. See §3.23 of control-spec.txt for how to do this correctly. Do not leave out the third step (“RESETCONF __OwningControllerProcess”) like chiiph did in Vidalia, or Tor will waste CPU and spam any info-level log destinations with “Monitored process (number) is still alive.” every 15 seconds.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#7667