[Rt-commit] rt branch, 4.4/update-rt-fulltext-indexer-quiet-option, updated. rt-4.4.4-457-g2f420afdf1
Blaine Motsinger
blaine at bestpractical.com
Fri May 21 19:36:14 EDT 2021
The branch, 4.4/update-rt-fulltext-indexer-quiet-option has been updated
via 2f420afdf151e40594819b1e0b05ed3b4ab573f5 (commit)
from c4b2b909f87bd6811b93413d44e32069e28e9848 (commit)
Summary of changes:
docs/full_text_indexing.pod | 25 +++++++++++--------------
1 file changed, 11 insertions(+), 14 deletions(-)
- Log -----------------------------------------------------------------
commit 2f420afdf151e40594819b1e0b05ed3b4ab573f5
Author: Blaine Motsinger <blaine at bestpractical.com>
Date: Fri May 21 18:35:07 2021 -0500
Update docs for rt-fulltext-indexer --quiet
diff --git a/docs/full_text_indexing.pod b/docs/full_text_indexing.pod
index 5b94399ebc..ab7c9613a6 100644
--- a/docs/full_text_indexing.pod
+++ b/docs/full_text_indexing.pod
@@ -47,11 +47,10 @@ To keep the index up-to-date, you will need to run:
tickets at a time; you can adjust this upwards by passing C<--limit
500>. Larger batch sizes will take longer and consume more memory.
-If there is already an instances of C<rt-fulltext-indexer> running, new
-ones will exit abnormally (with exit code 1) and the error message
-"rt-fulltext-indexer is already running." You can suppress this message
-and end those processes normally (with exit code 0) using the C<--quiet>
-option; this is particularly useful when running the command via
+If there is already an instance of C<rt-fulltext-indexer> running, new
+ones will exit with error message "rt-fulltext-indexer is already running."
+You can suppress this message and other output to C<STDERR> using the
+C<--quiet> option; this is particularly useful when running the command via
C<cron>:
/opt/rt4/sbin/rt-fulltext-indexer --quiet
@@ -98,11 +97,10 @@ To keep the index up-to-date, you will need to run:
tickets at a time; you can adjust this upwards by passing C<--limit
500>. Larger batch sizes will take longer and consume more memory.
-If there is already an instances of C<rt-fulltext-indexer> running, new
-ones will exit abnormally (with exit code 1) and the error message
-"rt-fulltext-indexer is already running." You can suppress this message
-and end those processes normally (with exit code 0) using the C<--quiet>
-option; this is particularly useful when running the command via
+If there is already an instance of C<rt-fulltext-indexer> running, new
+ones will exit with error message "rt-fulltext-indexer is already running."
+You can suppress this message and other output to C<STDERR> using the
+C<--quiet> option; this is particularly useful when running the command via
C<cron>:
/opt/rt4/sbin/rt-fulltext-indexer --quiet
@@ -251,10 +249,9 @@ C<--memory> option:
/opt/rt4/sbin/rt-fulltext-indexer --memory 10M
If there is already an instance of C<rt-fulltext-indexer> running, new
-ones will exit abnormally (with exit code 1) and the error message
-"rt-fulltext-indexer is already running." You can suppress this message
-and end those processes normally (with exit code 0) using the C<--quiet>
-option; this is particularly useful when running the command via
+ones will exit with error message "rt-fulltext-indexer is already running."
+You can suppress this message and other output to C<STDERR> using the
+C<--quiet> option; this is particularly useful when running the command via
C<cron>:
/opt/rt4/sbin/rt-fulltext-indexer --quiet
-----------------------------------------------------------------------
More information about the rt-commit
mailing list