X-Git-Url: http://git.liburcu.org/?a=blobdiff_plain;f=lttv%2Flttv%2Fsync%2FREADME;h=986885f8b52d9e0427f7c0b7da7a12d04a82f9bf;hb=277e5b535febfb81a5e9485b0d008e148b6979ac;hp=6e76ec17a24a62039d403ca7c295f7bd8ec9b546;hpb=48b641c1f6320eca569b2894f253d9d815250d45;p=lttv.git

diff --git a/lttv/lttv/sync/README b/lttv/lttv/sync/README
index 6e76ec17..986885f8 100644
--- a/lttv/lttv/sync/README
+++ b/lttv/lttv/sync/README
@@ -1,6 +1,6 @@
 Benjamin Poirier
 benjamin.poirier@polymtl.ca
-2009
+2009, 2010
 
 + About time synchronization
 This framework performs offline time synchronization. This means that the
@@ -137,8 +137,11 @@ eval is a special module, it doesn't really perform synchronization, instead
 it calculates and prints different metrics about how well traces are
 synchronized. Although it can be run like other analysis modules, it is most
 useful when run in a postprocessing step, after another synchronization module
-has been run. Eval is most common run in text mode. To do this, run
-lttv -m eval [usual options, ex: -t traces/node1 -t traces/node2 --sync ...]
+has been run. Eval is most common run in text mode. To do this, run:
+lttv -m sync_chain_batch [usual options, ex: -t traces/node1 -t traces/node2
+--sync ...]
+It can also be run from the lttv source tree via runlttv:
+./runlttv -m eval [usual runlttv options, ex: traces/node1 traces/node2]
 
 eval provides a few more options:
 --eval-rtt-file  -  argument: FILE