Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #4048

Closed
Open
Created Sep 19, 2011 by Roger Dingledine@arma

If Tor leaves behind its port.conf file, Vidalia and Tor race at next startup

If your Tor dies in an unclean way, its port.conf file stays around. Then the next time you run TBB, Vidalia says "is there a port.conf file? Why yes there is", and then reads it and uses the wrong ports.

Some users, e.g. on OS X, have reported this happening in practice.

Sometimes it works, since Tor writes a new one before Vidalia checks.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking