summaryrefslogtreecommitdiffstats
path: root/juniper
diff options
context:
space:
mode:
authorHenning Baldersheim <balder@yahoo-inc.com>2019-10-31 17:29:11 +0000
committerHenning Baldersheim <balder@yahoo-inc.com>2019-11-16 20:54:08 +0000
commitc11bd88ab54edd6e2c370ed7e82094707de19726 (patch)
treec18fae6b73be3dafd32cc7480cdd6b6aef0dab9c /juniper
parentb24dd074584ad83a547a81b95e19d49261d7b849 (diff)
Now fdispatch reliques can go
Diffstat (limited to 'juniper')
-rw-r--r--juniper/doc/written/fsearchparams.html11
1 files changed, 0 insertions, 11 deletions
diff --git a/juniper/doc/written/fsearchparams.html b/juniper/doc/written/fsearchparams.html
index 790d064480c..d27e4e66de8 100644
--- a/juniper/doc/written/fsearchparams.html
+++ b/juniper/doc/written/fsearchparams.html
@@ -445,17 +445,6 @@ variables such as
<p>
in the relevant rc file.
-Note that for a Data Search installation, the QR server has
-the responsibility of providing dynamic teasers, consequently the
-<tt>etc/qrserver/qrserverrc</tt> file should provide the above
-configuration.
-<p>
-For a similar Web Search configuration, using a "bare-bone" top level
-fdispatch instance, the <tt>fdispatchrc</tt> file is the appropriate place.
-<p>
-For a "standalone" Real-Time Search setup, the appropriate configuration
-file(s) is the fdispatch.addon file(s).
-
<h2>How to report bugs/errors related to Juniper</h2>
Errors/problems related to Juniper can be divided into two categories:
<ol>