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
  • #1101

Closed (moved)
(moved)
Open
Created Sep 21, 2009 by Roger Dingledine@arma

getinfo config-file doesn't handle relative paths well

Here's how getinfo config-file is supposed to go:

getinfo config-file 250-config-file=/usr/local/etc/tor/torrc 250 OK

But I started my tor like "path/to/tor -f moria2-orrc", so getinfo config-file simply returns "moria2-orrc" with no hint about where it is. That means controllers like arm don't know where to look.

Should we change Tor so it prepends an absolute path when answering the controller?

[Automatically added by flyspray2trac: Operating System: All]

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