<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Frequently Asked Questions
</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
TITLE="mnoGoSearch 3.3.10 reference manual"
HREF="index.html"><LINK
REL="UP"
TITLE="Introduction
"
HREF="msearch-intro.html"><LINK
REL="PREVIOUS"
TITLE="Contributors (in no particular order)
"
HREF="msearch-contriblist.html"><LINK
REL="NEXT"
TITLE="Installing mnoGoSearch
"
HREF="msearch-install.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
HREF="mnogo.css"><META
NAME="Description"
CONTENT="mnoGoSearch - Full Featured Web site Open Source Search Engine Software over the Internet and Intranet Web Sites Based on SQL Database. It is a Free search software covered by GNU license."><META
NAME="Keywords"
CONTENT="shareware, freeware, download, internet, unix, utilities, search engine, text retrieval, knowledge retrieval, text search, information retrieval, database search, mining, intranet, webserver, index, spider, filesearch, meta, free, open source, full-text, udmsearch, website, find, opensource, search, searching, software, udmsearch, engine, indexing, system, web, ftp, http, cgi, php, SQL, MySQL, database, php3, FreeBSD, Linux, Unix, mnoGoSearch, MacOS X, Mac OS X, Windows, 2000, NT, 95, 98, GNU, GPL, url, grabbing"></HEAD
><BODY
CLASS="sect1"
BGCOLOR="#EEEEEE"
TEXT="#000000"
LINK="#000080"
VLINK="#800080"
ALINK="#FF0000"
><!--#include virtual="body-before.html"--><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
><SPAN
CLASS="application"
>mnoGoSearch</SPAN
> 3.3.10 reference manual: Full-featured search engine software</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="msearch-contriblist.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 1. Introduction
<A
NAME="AEN11"
></A
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="msearch-install.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="faq"
>Frequently Asked Questions
<A
NAME="AEN378"
></A
></A
></H1
><P
></P
><UL
><LI
><P
> <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>How can I contribute to the project?
</I
></SPAN
>
</P
><P
>There are several ways you can help.
Please visit the
<A
HREF="http://www.mnogosearch.org/helpus.html"
TARGET="_top"
>Help Us page</A
>
on the <SPAN
CLASS="application"
>mnoGoSearch</SPAN
> website.
</P
></LI
><LI
><P
> <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>If I have pages with no keywords in the META description,
will the document get indexed?
</I
></SPAN
>
</P
><P
>Yes. By default <SPAN
CLASS="application"
>mnoGoSearch</SPAN
> indexes
the entire document. By changing the default values you can give
different weights to different parts of the document, like
<TT
CLASS="literal"
>body</TT
>,
<TT
CLASS="literal"
>title</TT
>,
<TT
CLASS="literal"
>keywords</TT
>,
<TT
CLASS="literal"
>description</TT
>.
</P
></LI
><LI
><P
> <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
> I'm wondering if <SPAN
CLASS="application"
>mnoGoSearch</SPAN
>
supports multi-byte character sets.
I'm especially interested in <TT
CLASS="literal"
>EUC-JP</TT
>.
</I
></SPAN
>
</P
><P
> Multi-byte character sets (including <TT
CLASS="literal"
>EUC-JP</TT
>)
are supported starting from the version <TT
CLASS="literal"
>3.2.x</TT
>.
</P
></LI
><LI
><P
> <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>Why does <SPAN
CLASS="application"
>indexer</SPAN
> fail with a message like
<TT
CLASS="literal"
>can't load library 'libmysqlclient.so.6'</TT
>?
</I
></SPAN
>
</P
><P
>You probably don't have <SPAN
CLASS="application"
>MySQL</SPAN
>
libraries properly installed. On Linux, just find out where
your <TT
CLASS="filename"
>libmysqlclient.so.6</TT
> is, then add
the path to this file into <TT
CLASS="filename"
>/etc/ld.so.conf</TT
>.
Then run <TT
CLASS="literal"
>ldconfig</TT
> as root.
</P
><P
>You can also set the value of the environment variable
<CODE
CLASS="varname"
>LD_LIBRARY_PATH</CODE
> to the path to the required
dynamic libraries. This works on any <ACRONYM
CLASS="acronym"
>OS</ACRONYM
>.
</P
><P
>Note that this is a general UNIX configuration issue,
not only <SPAN
CLASS="application"
>mnoGoSearch</SPAN
> specific.
</P
></LI
><LI
><P
> <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>What is the maximum data size
<SPAN
CLASS="application"
>mnoGoSearch</SPAN
> can can handle?
</I
></SPAN
>
</P
><P
>When using the <TT
CLASS="literal"
>blob</TT
> storage mode,
introduced in the version <TT
CLASS="literal"
>3.2.8</TT
>,
<SPAN
CLASS="application"
>mnoGoSearch</SPAN
>
is able to index and search through about one or two million
documents on a single computer.
The <SPAN
CLASS="application"
>mnoGoSearch cluster</SPAN
>
introduced in the version <TT
CLASS="literal"
>3.3.x</TT
> can distribute
data over multiple servers and is able to index up to about
<TT
CLASS="literal"
>500</TT
> million documents when using
<TT
CLASS="literal"
>256</TT
> machines.
</P
></LI
><LI
><P
> <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
> I want to index multiple virtual domains on a single box.
What settings do I need to change for that?
</I
></SPAN
>
</P
><P
> Virtual domains are fully supported.
No additional settings are required.
</P
></LI
><LI
><P
> <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
> Is it possible to use different templates for searches,
i.e. view search results in the design of different
sites without having to recompile
<SPAN
CLASS="application"
>search.cgi</SPAN
>?
</I
></SPAN
>
</P
><P
>There are several ways to do it.
They are given here in the order how
<SPAN
CLASS="application"
>search.cgi</SPAN
> detects template name:
</P
><P
></P
><OL
TYPE="1"
><LI
><P
> <SPAN
CLASS="application"
>search.cgi</SPAN
> checks
the environment variable <CODE
CLASS="varname"
>UDMSEARCH_TEMPLATE</CODE
>.
Thus you can put the desired search template file name
into this variable.
</P
></LI
><LI
><P
> <SPAN
CLASS="application"
>search.cgi</SPAN
> also supports
Apache internal redirect.
It checks the <CODE
CLASS="varname"
>REDIRECT_STATUS</CODE
> and
<CODE
CLASS="varname"
>REDIRECT_URL</CODE
> environment variables.
To activate this template option you may add these
lines to Apache <TT
CLASS="filename"
>srm.conf</TT
>:
</P
><P
> <PRE
CLASS="programlisting"
> AddType text/html .zhtml
AddHandler zhtml .zhtml
Action zhtml /cgi-bin/search.cgi
</PRE
>
</P
><P
>Put <SPAN
CLASS="application"
>search.cgi</SPAN
> into
your <TT
CLASS="filename"
>/cgi-bin/</TT
> directory.
Then put the <ACRONYM
CLASS="acronym"
>HTML</ACRONYM
> template
into your site directory
structure under any name with the <TT
CLASS="filename"
>.zhtml</TT
>
extension,
for example <TT
CLASS="filename"
>template.zhtml</TT
>.
Now you can open the search page:
<TT
CLASS="literal"
>http://www.site.com/path/to/template.zhtml</TT
>.
You can also use any available extension instead of
<TT
CLASS="literal"
>.zhtml</TT
>.
</P
></LI
><LI
><P
>If the above two methods fail,
<SPAN
CLASS="application"
>search.cgi</SPAN
> will open the template
having the same name with the script being executed,
using the <CODE
CLASS="varname"
>SCRIPT_NAME</CODE
> environment variable.
<SPAN
CLASS="application"
>search.cgi</SPAN
> will open the file
<TT
CLASS="filename"
>ETC/search.htm</TT
>,
<TT
CLASS="filename"
>search1.cgi</TT
> will
open <TT
CLASS="filename"
>ETC/search1.htm</TT
> and so on,
where <TT
CLASS="literal"
>ETC</TT
> is
<SPAN
CLASS="application"
>mnoGoSearch</SPAN
> <TT
CLASS="literal"
>/etc</TT
>
directory
(usually <TT
CLASS="literal"
>/usr/local/mnogosearch/etc</TT
>).
So, you can use the same <SPAN
CLASS="application"
>search.cgi</SPAN
>
with different templates
without having to recompile it. Just create one or multiple
hard or symbolic links to <SPAN
CLASS="application"
>search.cgi</SPAN
>
or copy it under different names then put the corresponding
search templates into the <TT
CLASS="filename"
>/etc</TT
>
directory of your <SPAN
CLASS="application"
>mnoGoSearch</SPAN
> installation.
</P
></LI
></OL
></LI
><LI
><P
> <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
><SPAN
CLASS="application"
>indexer</SPAN
>
doesn't store some links in
the database although they are expected to be stored.
<SPAN
CLASS="application"
>indexer</SPAN
> doesn't grab all the
links from my web site,
as a result only half the site is indexed.
</I
></SPAN
>
</P
><P
>There are two possible reasons:</P
><P
></P
><OL
TYPE="1"
><LI
><P
><SPAN
CLASS="application"
>indexer</SPAN
> finds the links,
but rejects to put them into the database.
This most likely means that your <TT
CLASS="filename"
>indexer.conf</TT
>
configured not to allow these links.
</P
></LI
><LI
><P
><SPAN
CLASS="application"
>indexer</SPAN
> doesn't
find the links on the page because of a bug
in the <ACRONYM
CLASS="acronym"
>HTML</ACRONYM
> parser.
</P
></LI
></OL
><P
>Imaging that
<TT
CLASS="literal"
>http://localhost/links.html</TT
> is a
page that contains ignored links.
</P
><P
>To discover the reason,
start <SPAN
CLASS="application"
>indexer</SPAN
> with these
command line arguments:
</P
><P
> <KBD
CLASS="userinput"
>indexer -am -u http://localhost/links.html</KBD
>
</P
><P
>It will display various debug information, including:
</P
><P
></P
><UL
><LI
><P
>every link found on this page found
</P
></LI
><LI
><P
>information why <SPAN
CLASS="application"
>indexer</SPAN
>
rejects or accepts every link found
</P
></LI
></UL
><P
>With this information provided it is easy to detect
what is the reason of unexpected <SPAN
CLASS="application"
>indexer</SPAN
>
behavior: either 1 or 2. When you know the reason, you can either
change your <TT
CLASS="filename"
>indexer.conf</TT
> and check again,
or file a bug if you're sure that <TT
CLASS="filename"
>indexer.conf</TT
>
is OK.
</P
><P
>When <A
HREF="http://www.mnogosearch.org/bugs/"
TARGET="_top"
> reporting this sort of bugs</A
>, please include
<TT
CLASS="literal"
>indexer -am -u http://localhost/links.html</TT
> output,
as well as the <B
CLASS="command"
>Server/Realm</B
>
and the <B
CLASS="command"
>Allow/Disallow</B
> commands
from your <TT
CLASS="filename"
>indexer.conf</TT
>.
</P
></LI
></UL
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="msearch-contriblist.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="msearch-install.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Contributors (in no particular order)
<A
NAME="AEN236"
></A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="msearch-intro.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Installing <SPAN
CLASS="application"
>mnoGoSearch</SPAN
>
<A
NAME="AEN519"
></A
></TD
></TR
></TABLE
></DIV
><!--#include virtual="body-after.html"--></BODY
></HTML
>
