[tor-bugs] #1101 [Tor Client]: getinfo config-file doesn't handle relative paths well

[Tor Bug Tracker & Wiki]

#1101: getinfo config-file doesn't handle relative paths well
--------------------------------+-------------------------------------------
 Reporter:  arma                |         Type:  defect    
   Status:  new                 |     Priority:  minor     
Milestone:  Tor: 0.2.3.x-final  |    Component:  Tor Client
  Version:  0.2.1.19            |   Resolution:  None      
 Keywords:  easy                |       Parent:            
--------------------------------+-------------------------------------------
Changes (by nickm):

  * milestone:  => Tor: 0.2.3.x-final


Old description:

> 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]

New description:

 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]

--

Comment:

 Yes, I think so.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1101#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online