DataparkSearch indexer uses syslog to log its messages. Different verbose levels could be specified with -v option or by LogLevel command in config files:
Table 3-2. Verbose levels
| 0 | SILENT | suppress all log. Bad idea, better use -l option. |
| 1 | ERROR | log only critical errors |
| 2 | WARNING | log warnings as well |
| 3 | INFO | add info messages to log. Default. |
| 4 | EXTRA | extra logging |
| 5 | DEBUG | for debug purposes |
You may use -l option to suppress log to stdout/stderr when running indexer via crontab. Without -l option log is sent both to stdout/stderr and to log files. If you do not like such behavior, run configure with --disable-syslog flag and recompile indexer. Compiled without syslog support, indexer uses only stdout/stderr.
Syslog uses different facilities to separate log messages. The indexer's default facility is LOCAL7. Facility could be changed during configure with --enable-syslog=LOG_FACILITY option. LOG_FACILITY should be one of the standard facilities, usually listed in /usr/include/sys/syslog.h header file.
Facility helps to separate DataparkSearch messages from others. You can modify /etc/syslog.conf to tell syslog how to treat DataparkSearch messages. For example:
# Log all messages from DataparkSearch to separate file local7.* -/var/log/DataparkSearch.log
Other example:
# Send all DataparkSearch messages to host named central # Syslog on central should be configured to allow this local7.* @central
By default all messages are logged to /var/log/messages as well. DataparkSearch could populate this file with a number of messages. To avoid this, add local7.none or local7.!* (ignore any messages from local7 facility) to your 'catch-all' log files.
For example:
#
# Some `catch-all' logfiles.
#
*.=info;*.=notice;*.=warn;\
auth,authpriv.none;\
cron,daemon.none;\
mail,news.none;\
local7.!* -/var/log/messages
Please take a look at syslogd(8) and syslog.conf(5) man pages for more detailed information about syslog and its configuration notes.