force the admin to mkdir the datadirectory himself,

so he gets the permissions right.

also this means clients will never need to make the datadirectory.

also remind the admin to fix his clock before setting up his node.

svn:r650

diff --git a/Makefile.am b/Makefile.am
index 47ddde068d504c0e1671dd5b89153f01921d4ee0..3926fc794ce9a8886a7e2d182b7cd5909ad5930e 100644 (file)
--- a/Makefile.am
+++ b/Makefile.am
@@ -5,5 +5,5 @@ DIST_SUBDIRS = src doc
 
 EXTRA_DIST = LICENSE
 
-install-data-local:
-       $(INSTALL) -m 755 -d $(LOCALSTATEDIR)/lib/tor
+#install-data-local:
+#      $(INSTALL) -m 755 -d $(LOCALSTATEDIR)/lib/tor

diff --git a/README b/README
index fbe27b611d76aaf6f58f997fbec536e9bd692a97..1f1e13eaaa7b152228f7a84e9a3c5f38a95bcfda 100644 (file)
--- a/README
+++ b/README
@@ -17,10 +17,13 @@ doesn't work for you.
 
 Do you want to run a tor server?
 
-  First, move sample-server-torrc onto torrc, and edit it. Then run tor
-  to generate keys. One of the generated files is your 'fingerprint' file.
-  Mail it to arma@mit.edu. Remember that you won't be able to authenticate
-  to the other tor nodes until I've added you to the directory.
+  First, move sample-server-torrc onto torrc, and edit it. Create the
+  DataDirectory, and make sure it's owned by whoever will be running
+  tor. Fix your system clock so it's not too far off. Then run tor
+  to generate keys. One of the generated files is your 'fingerprint'
+  file. Mail it to arma@mit.edu. Remember that you won't be able to
+  authenticate to the other tor nodes until I've added you to the
+  directory.
 
 Configuring tsocks: