[tor-commits] [tor/master] Document the case of HiddenServiceDir being defined as relative path.

[nickm@xxxxxxxxxxxxxx]

commit f785723e0b76f1b049b6103d01c316778445b33f
Author: rl1987 <rl1987@xxxxxxxxxxxxxxxx>
Date:   Sun Dec 21 19:05:10 2014 +0200

    Document the case of HiddenServiceDir being defined as relative path.
---
 changes/bug13913 |    5 +++++
 doc/tor.1.txt    |    2 ++
 2 files changed, 7 insertions(+)

diff --git a/changes/bug13913 b/changes/bug13913
new file mode 100644
index 0000000..7d908bd
--- /dev/null
+++ b/changes/bug13913
@@ -0,0 +1,5 @@
+  o Documentation:
+    - Clarify HiddenServiceDir option description in manpage to make it
+      clear that directory in question is relative to current working 
+      directory of Tor instance if it is defined as a relative path. Fixes
+      issue 13913.
diff --git a/doc/tor.1.txt b/doc/tor.1.txt
index e876829..92f0407 100644
--- a/doc/tor.1.txt
+++ b/doc/tor.1.txt
@@ -2025,6 +2025,8 @@ The following options are used to configure a hidden service.
     Store data files for a hidden service in DIRECTORY. Every hidden service
     must have a separate directory. You may use this option  multiple times to
     specify multiple services. DIRECTORY must be an existing directory.
+    NB: if DIRECTORY is defined in relative way, it will be relative to current
+    working directory of Tor instance, not it's DataDirectory.
 
 [[HiddenServicePort]] **HiddenServicePort** __VIRTPORT__ [__TARGET__]::
     Configure a virtual port VIRTPORT for a hidden service. You may use this



_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits