diff options
Diffstat (limited to 'rt/docs/full_text_indexing.pod')
| -rw-r--r-- | rt/docs/full_text_indexing.pod | 21 |
1 files changed, 19 insertions, 2 deletions
diff --git a/rt/docs/full_text_indexing.pod b/rt/docs/full_text_indexing.pod index 0952b4eb9..6b0025d62 100644 --- a/rt/docs/full_text_indexing.pod +++ b/rt/docs/full_text_indexing.pod @@ -48,8 +48,16 @@ To keep the index up-to-date, you will need to run: ...at regular intervals. By default, this will only tokenize up to 100 tickets at a time; you can adjust this upwards by passing C<--limit 500>. Larger batch sizes will take longer and -consume more memory. Care should be taken to ensure that multiple -instances of C<rt-fulltext-indexer> are not run at the same time. +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 +C<cron>: + + sbin/rt-fulltext-indexer --quiet =head1 MYSQL @@ -165,6 +173,15 @@ C<--memory> option: 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 +C<cron>: + + sbin/rt-fulltext-indexer --quiet + Instead of being run via C<cron>, this may instead be run via a DBMS_JOB; read the B<Managing DML Operations for a CONTEXT Index> chapter of Oracle's B<Text Application Developer's Guide> for details |