=====================
= COMPILING FREE-SA =
=====================

Q:  Do I need GNU or BSD make to build free-sa?
A:  No, you don't. Any make should work.

Q:  Do I need GNU C compiler to build free-sa?
A:  No, you don't. Any cc should work.

Q:  Do I need bash, csh or ksh to build free-sa?
A:  No, you don't. Any POSIX sh should work.

Q:  Do I need any other tool to build free-sa?
A:  No, you don't. But for proper install you need GNU like install (you may use
    SAinstall.sh provided in free-sa distribution).

Q:  When compiling I got error "cc1: unknown C standard 'c99'".
A:  Your GNU C compiler is obsolete. Update it or remove line in config.mk
    containing -std=c99.

Q:  What optimization options may i use?
A:  Enable at global.mk your compiler specific options. For gcc uncomment all
    and set MARCH as close as possible to your target arch (check gcc man page).
    If you use gcc and compile on your target platform for using free-sa then 
    set MARCH to native, this will give you maximal performance.

===================
= RUNNING FREE-SA =
===================

Q:  When running free-sa I got error "Too many open files".
A:  Because free-sa uses 2 file descriptors per user. To resolve this add next
    string to your free-sa start script (before free-sa line):
    ulimit -n X
    where X - number of users multiplied by 2.

Q:  Why I got in reports strange symbol as thousands separator?
    (especially with ru_RU.UTF8 locale)
A:  Because your locale files define it as thousands separator.
    There is 2 ways to resolve this:
    1. Update locale definitions files within your system distro.
    2. Remake locale files with changed by yourself thousands separator.
    3. Switch to other locale.

Q:  Free-SA is really fast, but i want more speed (lesser CPU load for CGI).
A:  1. Use fastest (often native is better) compiler for your platform, also
       check COMPILING FREE-SA section in this FAQ.
    2. Set DEBUG to 0 in global.mk when compiling (it's default).
    3. Disable unneeded features in free-sa config file (especially fullurl).
    4. Specify log format in free-sa config file manually (autodetection takes
       some time, especially for mail logs).
    5. If downloads/usertab/global_filter files is empty, then remove
       appropriate options from free-sa config file.
    6. Parsing takes some time, so the lesser lines (comments, options, etc) in
       free-sa configuration file exists the better is perfomance on old PC.
    7. Use singlebyte locale, not multibyte.

=================
= USING FREE-SA =
=================

Q:  Is there any 'hidden' features?
A:  Yes, there is one. To use it, generate reports with fullurl="true" option,
    then open user report with full urls and move mouse over any search request.
    You must see user search request in clear text within pop-uped box.
    Currently this feature support next search engines: google.com, yandex.ru
    and rambler.ru and only English and Russian languages (others is untested).

Q:  How may I generate report from multiple log files using Free-SA?
A:  There is one long, but Unix way (you may even create script with all those 
    things in it for crond or manual run):
    1. Create a named pipe (do not forgot about '-m' option to be on secure way):
	mkfifo -m 0600 /tmp/free-sa.pipe
    2. Now use cat (on clear text log files) or zcat (on log files compressed by
       gzip) or bzcat (log files compressed by bzip2) to redirect log files data
       to created pipe at 1st step (pass them in date order):
	cat accss010107.log accss020107.log accss030107.log > /tmp/free-sa.pipe
       Note: At this step cat will freeze, it's ok.
    3. Run free-sa (free-sa option -d not tested in this configuration, I
       also recommend to disable log format autodetection feature in free-sa 
       configuration file free-sa.conf):
	free-sa -l /tmp/free-sa.pipe
    4. Now you may remove pipe, or leave it for next runs of free-sa in such
       configuration.
