# HG changeset patch
# User jbe
# Date 1363611001 -3600
# Node ID 0f5841ef67c62d2ef99cc940bf097f606ed28ddc
# Parent  54e2a6e63a945b62aa76ea06a1ad7b2ee27c54d8
Updated README file to include information on lf_update_suggestion_order

diff -r 54e2a6e63a94 -r 0f5841ef67c6 README
--- a/README	Mon Mar 18 11:40:53 2013 +0100
+++ b/README	Mon Mar 18 13:50:01 2013 +0100
@@ -9,16 +9,23 @@
 Compile lf_update binary:
 $ make
 
-Ensure that "lf_update dbname=liquid_feedback" is called regularly!
+Ensure that "lf_update dbname=liquid_feedback" and
+"lf_update_suggestion_order dbname=liquid_feedback" are called
+regularly! It is required to run these commands regularly
+(i.e. every 5 minutes via cron) to update cached supporter counts,
+to change the state of issues when neccessary, to calculate the
+result of votings, etc.  If you wish, copy the created lf_update
+and lf_update_suggestion_order files to /usr/local/bin or a
+similar directory.
 
-It is required that lf_update is executed regulary (i.e. every
-5 minutes via cron) to update cached supporter counts, to change
-the state of issues when neccessary, and to calculate the result
-of votings. If you wish, copy the created lf_update file to
-/usr/local/bin or a similar directory.
+It is possible to run these two commands in parallel, if a setup
+requires splitting the load to multiple processor cores. In other
+cases it is recommended to run "lf_update" first, and then
+"lf_update_suggestion_order".
 
-On successful run, lf_update will not produce any output
-and exit with code 0.
+On successful run, these commands will not produce any output
+and exit with code 0. The command "lf_update_suggestion_order" may
+be called with a first argument of "-v" to print log output.
 
 NOTE: When writing to the database, some INSERTs must be executed
       within the same transaction, e.g. issues can't exist without