Opened 13 years ago

Last modified 7 years ago

#229 closed defect (Implemented)

relative path to torrc makes tor sad

Reported by: weasel Owned by:
Priority: Low Milestone: 0.1.1.11-alpha
Component: Core Tor/Tor Version: 0.1.1.10-alpha
Severity: Keywords:
Cc: weasel Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Tue 19:33:06 <weasel> when you start it with tor -f torrc
Tue 19:33:15 <weasel> and it chdirs into its DataDirectory
Tue 19:33:22 <weasel> and then you send it a SIGHUP
Tue 19:33:28 <weasel> it says
Tue 19:33:28 <weasel> Jan 03 19:32:22.159 [warn] Unable to open configuration file "torrc".
Tue 19:33:30 <weasel> and dies
Tue 19:33:36 <nickm> ooh.
Tue 19:33:51 <nickm> what's the right behavior, do you think?
Tue 19:34:05 <nickm> To remember the original cwd and resolve relative torrc paths relative to that?
Tue 19:34:33 <weasel> yes, probably

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (5)

comment:1 Changed 13 years ago by nickm

This is a little more worrisome than it might seem at first. There can be more than one relative path,
after all: there might be more in the config file.

comment:2 Changed 13 years ago by nickm

Maybe we should warn and quit if we're a daemon and torrc is relative.

comment:3 Changed 13 years ago by weasel

the very same problems occur when you aren't a daemon.

comment:4 Changed 13 years ago by nickm

flyspray2trac: bug closed.
Warning implemented in CVS

comment:5 Changed 7 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.