windows torrc references @CONFDIR@/tor-exit-notice.html

Two issues:

1. we should not ship the torrc with @CONFDIR@ in it.
2. we should include the tor-exit-notice.html file and set the whole config option correctly.

A user should simply have to uncomment this line to make it work. Most likely, CONFDIR is C:\Documents and Settings\username\Application Data\Tor.

changed milestone to %Tor: unspecified

added component::core tor/tor milestone::Tor: unspecified priority::medium resolution::worksforme severity::normal status::closed tor-relay type::defect version::tor unspecified windows labels

Trac:
Description: Two issues:

1. we should not ship the torrc with @CONFDIR@ in it.
2. we should include the tor-exit-notice.html file and set the whole config option correctly.

All a user should have to do is to uncomment the line to have it work.

to

Two issues:

1. we should not ship the torrc with @CONFDIR@ in it.
2. we should include the tor-exit-notice.html file and set the whole config option correctly.

A user should simply have to uncomment this line to make it work. Most likely, CONFDIR is C:\Documents and Settings\username\Application Data\Tor.

See also #2006 (moved) and comments there

For all the files in our configuration

Trac:
Milestone: N/A to Tor: 0.2.3.x-final

Argh, I should finish the thought. We should change our configuration file format so that we can get filenames with some variables that in them that are resolved at runtime. We already support that to some extent for filenames that start with ~ and ~uname on unix.

Trac:
Points: N/A to N/A
Keywords: N/A deleted, windows added
Actualpoints: N/A to N/A

Nick has clarified that this is a documentation bug. [comment:4 Comment 4] describes a feature request which has now been split out into #5208 (moved).

Trac:
Milestone: Tor: 0.2.3.x-final to Tor: unspecified

Trac:
Keywords: windows deleted, windows tor-relay added

Trac:
Component: Tor Relay to Tor

Trac:
Sponsor: N/A to N/A
Status: new to closed
Resolution: N/A to worksforme
Reviewer: N/A to N/A
Severity: N/A to Normal

(I believe this got resolved by one of our packaging revamps)

closed

mentioned in issue #2006 (moved)

mentioned in issue #5208 (moved)

moved to tpo/core/tor#2005 (closed)

mentioned in issue tpo/core/tor#5208 (closed)