stackforge/tomograph
Code Issues Proposed changes

indent code further so markdown formats it as code

Browse Source 
explain the setsid thing
This commit is contained in:
Tim Daly, Jr
2013-04-23 01:37:33 +00:00
parent 3ada50c6fd
commit 5771d5199b
1 changed files with 36 additions and 37 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
doc/openstack-patches/README.md
View File

@@ -12,7 +12,6 @@ Tracing Openstack with Tomograph
3. Apply tomograph patches to Openstack:
cd nova; patch -p1 < tomograph/doc/openstack-patches/nova-stable-folsom.patch
cd keystone; patch -p1 < tomograph/doc/openstack-patches/keystone-stable-folsom.patch
cd glance; patch -p1 < tomograph/doc/openstack-patches/glance-stable-folsom.patch
@@ -37,7 +36,7 @@ Tracing Openstack with Tomograph
Viewing Traces in Zipkin
------------------------
====================
1. Set up cassandra, (something like the following):
@@ -54,7 +53,7 @@ Viewing Traces in Zipkin
git clone git://github.com/twitter/zipkin.git
apache-cassandra-1.2.3/bin/cassandra-cli -host localhost -port 9160 -f zipkin/zipkin-cassandra/src/schema/cassandra-schema.txt
3. Start the zipkin components:
3. Start the zipkin components. Note, you should wait until the build for each component is done before starting the next one, because sbt does not seem to handle multiple builds running in the same directory very well. We use setsid instead of nohup because sbt seems to try to frob the terminal so it gets a SIGTTOU and stops otherwise:
cd zipkin
setsid bin/collector &> collector-out