Modified the README for keystone-control issue

1 files changed, 13 insertions, 2 deletions

diff --git a/README b/README
index 033ec174..824fa679 100644
--- a/README
+++ b/README
@@ -67,6 +67,9 @@ During  development, you can simply run
 
 It dumps stdout and stderr onto the terminal.
 
+
+RUNNING KEYSOTNE IN AS ROOT IN PRODUCTION
+---------------------------------------------
 In production, stdout and stderr need to be closed and all theoutput needs tobe redirected to a log file.
 Once the package is installed through setup tools, RPM, deb, or ebuild keystone-control is installed 
 as /usr/sbin/keystone-control. Typically, it will be started a script in /etc/init.d/keystoned
@@ -82,7 +85,10 @@ It writes the process id of the daemon into /var/run/keystone/keystine-auth.pid.
 keystone-control has the infrastructure to start and stop multiple servers keystone-xxx  
 
 
-The developenmt of keystone-control itself can be done like this
+DEVELOPMENT OF keystone-control
+-------------------------------
+
+During the  development of keystone-control can be started as a user instead of root
 
 From the topdir 
 
@@ -92,11 +98,16 @@ config.py takes the config file from topdir/etc/keystone.conf
 
 If the keystone package is also intalled on the system
 /etc/keystone.conf or /etc/keystone/keystone.conf has higher priority
-than top_dir/etc/keystone.conf. If you are also doing development on a
+than <top_dir>/etc/keystone.conf. If you are also doing development on a
 system that has keystone.conf installed in /etc/you need to disambiguate it by
 
      $ bin/keystone-control --confg-file etc/keystone.conf  --pid-file pidfile auth <start|stop|restart>
 
+Also, keystone-control calls keystone-auth and it need to be in the PATH
+
+     $ export PATH=<top_dir>/bin:$PATH
+
+
 
 RUNNING TEST SERVICE:
 ---------------------