use dlog-daemon.sh to start writeproxy, use the newly created my_name…

…space to write logs. (#22)

.gitignore

@@ -21,3 +21,5 @@ lib/
 *~
 *#*#
 *.#*
+dist/
+logs/

distributedlog-service/bin/dlog-daemon.sh

@@ -43,7 +43,7 @@ fi
 
 # DLOG logging configuration
 DLOG_LOG_DIR=${DLOG_LOG_DIR:-"$DL_HOME/logs"}
-DLOG_ROOT_LOGGER=${DLOG_ROOT_LOGGER:-'INFO,ROLLINGFILE'}
+DLOG_ROOT_LOGGER=${DLOG_ROOT_LOGGER:-'INFO,R'}
 # Process Control Parameters
 DLOG_STOP_TIMEOUT=${DLOG_STOP_TIMEOUT:-30}
 DLOG_PID_DIR=${DLOG_PID_DIR:-$DL_HOME/pids}

docs/basics/introduction.rst

@@ -60,7 +60,7 @@ Namespaces
 The *log streams* belong to same organization are usually categorized and managed under
 a **namespace**. A DL **namespace** is basically for applications to locate where the
 *log streams* are. Applications could *create* and *delete* streams under a namespace,
-and also be able to *truncate* a stream to given sequence number (either *DLSN* *TransactionID*).
+and also be able to *truncate* a stream to given sequence number (either *DLSN* or *TransactionID*).
 
 Writers
 -------

docs/basics/quickstart.rst

@@ -53,15 +53,15 @@ Let's create 5 log streams, prefixed with `messaging-test-`.
 
 ::
 
-    > ./distributedlog-service/bin/dlog tool create -u distributedlog://127.0.0.1:7000/messaging/distributedlog -r messaging-stream- -e 1-5
+    > ./distributedlog-service/bin/dlog tool create -u distributedlog://127.0.0.1:7000/messaging/my_namespace -r messaging-stream- -e 1-5
 
 
 We can now see the streams if we run the `list` command from the tool.
 
 ::
     
-    > ./distributedlog-service/bin/dlog tool list -u distributedlog://127.0.0.1:7000/messaging/distributedlog
-    Streams under distributedlog://127.0.0.1:7000/messaging/distributedlog :
+    > ./distributedlog-service/bin/dlog tool list -u distributedlog://127.0.0.1:7000/messaging/my_namespace
+    Streams under distributedlog://127.0.0.1:7000/messaging/my_namespace :
     --------------------------------
     messaging-stream-1
     messaging-stream-3
@@ -74,11 +74,11 @@ We can now see the streams if we run the `list` command from the tool.
 Step 5: Start a write proxy
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Now, lets start a write proxy server that serves writes to distributedlog namespace `distributedlog://127.0.0.1/messaging/distributedlog`. The server listens on 8000 to accept fan-in write requests.
+Now, lets start a write proxy server that serves writes to distributedlog namespace `distributedlog://127.0.0.1/messaging/my_namespace`. The server listens on 8000 to accept fan-in write requests.
 
 ::
     
-    > ./distributedlog-service/bin/dlog com.twitter.distributedlog.service.DistributedLogServerApp -p 8000 --shard-id 1 -sp 8001 -u distributedlog://127.0.0.1:7000/messaging/distributedlog -mx -c ${DL_HOME}/distributedlog-service/conf/distributedlog_proxy.conf
+    > ./distributedlog-service/bin/dlog-daemon.sh start writeproxy -p 8000 --shard-id 1 -sp 8001 -u distributedlog://127.0.0.1:7000/messaging/my_namespace -mx -c `pwd`/distributedlog-service/conf/distributedlog_proxy.conf
 
 
 Step 6: Tail reading records
@@ -88,7 +88,7 @@ The distributedlog tutorial has a multi-streams reader that will dump out receiv
 
 ::
     
-    > ./distributedlog-tutorials/distributedlog-basic/bin/runner run com.twitter.distributedlog.basic.MultiReader distributedlog://127.0.0.1:7000/messaging/distributedlog messaging-stream-1,messaging-stream-2,messaging-stream-3,messaging-stream-4,messaging-stream-5
+    > ./distributedlog-tutorials/distributedlog-basic/bin/runner run com.twitter.distributedlog.basic.MultiReader distributedlog://127.0.0.1:7000/messaging/my_namespace messaging-stream-1,messaging-stream-2,messaging-stream-3,messaging-stream-4,messaging-stream-5
 
 
 Step 7: Write some records