[or-cvs] r20018: {torflow} creating a new bwauth scanning user is not optional. at leas (torflow/trunk/NetworkScanners/BwAuthority)

[arma@xxxxxxxx]

Author: arma
Date: 2009-07-14 18:36:37 -0400 (Tue, 14 Jul 2009)
New Revision: 20018

Modified:
   torflow/trunk/NetworkScanners/BwAuthority/README.BwAuthorities
Log:
creating a new bwauth scanning user is not optional. at least,
not with the scripts as they are currently.


Modified: torflow/trunk/NetworkScanners/BwAuthority/README.BwAuthorities
===================================================================
--- torflow/trunk/NetworkScanners/BwAuthority/README.BwAuthorities	2009-07-14 19:23:16 UTC (rev 20017)
+++ torflow/trunk/NetworkScanners/BwAuthority/README.BwAuthorities	2009-07-14 22:36:37 UTC (rev 20018)
@@ -86,13 +86,14 @@
 any other users from writing the file there.
 
 
-6. (Optional) Create a user capable of writing the bwscan file
+6. Create a new user capable of writing the bwscan file
 
-This can either be the user that will run the scanning scripts, 
-or the user that will receive the scp of the result from the remote
-machine. It should have write access to your bwscan dir from
-step 4.
+You will need to run the scanning scripts as a separate user. That's
+because the scripts run commands like 'killall tor' and expect it not
+to affect any other tor processes.
 
+The new user should have write access to your bwscan dir from step 4.
+
 # useradd bwscanner
 # chown toruser:bwscanner /var/lib/tor.bwscans/
 # chmod 770 /var/lib/tor.bwscans/