Thread: [cvs] bogofilter/doc README.db,1.35,1.35.16.1 bogofilter-faq.html,1.137,1.137.24.1
Fast Bayesian spam filter along lines suggested by Paul Graham
Brought to you by:
m-a
From: David R. <re...@us...> - 2005-11-30 04:09:44
|
Update of /cvsroot/bogofilter/bogofilter/doc In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv25009/doc Modified Files: Tag: Branch-1_0_0 README.db bogofilter-faq.html Log Message: Sync with HEAD. Index: bogofilter-faq.html =================================================================== RCS file: /cvsroot/bogofilter/bogofilter/doc/bogofilter-faq.html,v retrieving revision 1.137 retrieving revision 1.137.24.1 diff -u -d -r1.137 -r1.137.24.1 --- bogofilter-faq.html 20 Jun 2005 23:30:39 -0000 1.137 +++ bogofilter-faq.html 30 Nov 2005 04:09:35 -0000 1.137.24.1 @@ -53,6 +53,17 @@ <p>This document is intended to answer frequently asked questions about bogofilter.</p> + <h2>Typographic conventions</h2> + <ul><li>If we show example commands that start with a + dollar sign ($), this means that these commands should be executed + by an unprivileged user, NOT the root user.</li> + <li>If we show example commands that start with a hash mark (#), + this means that these commands need to be executed by the root + user.</li> + </ul> + + <h1>Frequently asked questions and their answers</h1> + <ul> <li> General Information @@ -73,7 +84,7 @@ <li><a href="#production">How can I keep the scoring accuracy high?</a></li> <li><a href="#mboxformats">What mailbox (file) formats does bogofilter understand?</a></li> <li><a href="#vvv">What does bogofilter's verbose output mean?</a></li> - <li><a href="#unisure">What is <i>Unsure</i> mode?</a></li> + <li><a href="#unsure">What is <i>Unsure</i> mode?</a></li> <li><a href="#train-on-error">What are "training on error" and "training to exhaustion"?</a></li> <li><a href="#autoupdate">What does the '-u' (autoupdate) switch do?</a></li> @@ -1267,7 +1278,7 @@ <p>If you don't already have a v3.0+ version of <a href="http://www.sleepycat.com/">BerkeleyDB</a>, then <a href="http://www.sleepycat.com/download/db/">download it (take - one of the 4.2.X versions)</a>, + one of the 4.4.X, 4.3.X or 4.2.X versions)</a>, unpack it, and do these commands in the db directory:</p> <pre> $ cd build_unix $ sh ../dist/configure @@ -1280,8 +1291,13 @@ <h3>On Solaris</h3> + <p>Be sure that your PATH environment variable begins with + /usr/xpg6/bin:/usr/xpg4/bin:/usr/ccs/bin (/usr/xpg6/bin is only + present on Solaris 10 and can be omitted on Solaris 9 and older + versions). That is required for POSIX compliance.</p> + <p>Unpack it, and then do:</p> - <pre> $ ./configure --with-libdb-prefix=/usr/local/BerkeleyDB.4.2 + <pre> $ ./configure --with-libdb-prefix=/usr/local/BerkeleyDB.4.4 $ make # make install-strip</pre> @@ -1290,25 +1306,37 @@ variable before you start bogofilter. On newer systems, the most convenient way is probably to use the crle(1) tool to set the path permanently so BerkeleyDB is available to all applications.</p> - <pre> $ LD_LIBRARY_PATH=/usr/lib:/usr/local/lib:/usr/local/BerkeleyDB.4.2 + <pre> $ LD_LIBRARY_PATH=/usr/lib:/usr/local/lib:/usr/local/BerkeleyDB.4.4 $ export LD_LIBRARY_PATH</pre> - <p>Note that some "make" versions shipped with Solaris break when - you try to build bogofilter outside of its source directory. - Either build in the source directory (as suggested above) or - use GNU make (gmake).</p> + <p>Note that some "make" versions shipped with older Solaris version + break when you try to build bogofilter outside of its source + directory. Either build in the source directory (as suggested + above) or use GNU make (gmake).</p> + + <p>If your Solaris GCC complains with "ld: fatal: file values-Xa.o: + open failed: No such file or directory", install the SUNWarc + package.</p> <h3>On FreeBSD</h3> - <p>The FreeBSD ports and packages carry the latest stable versions of + <p>The FreeBSD ports collection carries the latest stable versions of bogofilter. This approach uses the highly recommended - portupgrade and cvsup software packages. To install these two - fine pieces, type (you need to do this only once):</p> - <pre> # pkg_add -r portupgrade cvsup</pre> + portupgrade and portsnap software packages. To install portupgrade, + type (you need to do this only once), as root:</p> + <pre> # pkg_add -r portupgrade</pre> + + <p>On newer FreeBSD releases, portsnap is in the base system. If + typing <kbd>portsnap help</kbd> does not print portsnap's help, you + need to install portsnap from ports. To achieve that, type (you need + to do this only once), as root:</p> + <pre> # pkg_add -r portsnap</pre> <p>To install or upgrade bogofilter, just - <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html">upgrade your portstree using cvsup</a>, - then type:</p> + <a + href="http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/portsnap.html">upgrade + your portstree using portsnap</a>, + then type, as root:</p> <pre> # portupgrade -N bogofilter</pre> <p><em>Note: This assumes you are root.</em> If not, read through @@ -1318,12 +1346,19 @@ <p>Depending on your system you may have to set some environment variables for the <code>./configure</code> command. Example:</p> - <pre> # env CPPFLAGS=-I/usr/local/include/db3 LIBS=-ldb3 LDFLAGS=-L/usr/local/lib ./configure</pre> + <pre> $ env CPPFLAGS=-I/usr/local/include/db3 LIBS=-ldb3 LDFLAGS=-L/usr/local/lib ./configure</pre> <p>The actual paths you use here depend on your system and the database versions you have installed. Check and replace accordingly.</p> + <h3>On NetBSD and other systems that use "pkgsrc"</h3> + + <p>pkgsrc should be offering a reasonably recent stable bogofilter + release. See <a + href="http://www.pkgsrc.org/">http://www.pkgsrc.org/</a> for + information on pkgsrc.</p> + <h3>On HP-UX</h3> <p>See the file Index: README.db =================================================================== RCS file: /cvsroot/bogofilter/bogofilter/doc/README.db,v retrieving revision 1.35 retrieving revision 1.35.16.1 diff -u -d -r1.35 -r1.35.16.1 --- README.db 16 Aug 2005 11:45:58 -0000 1.35 +++ README.db 30 Nov 2005 04:09:35 -0000 1.35.16.1 @@ -57,7 +57,8 @@ Sleepycat Software: Berkeley DB 4.0.14: (November 18, 2001) Sleepycat Software: Berkeley DB 4.1.25: (December 19, 2002) Sleepycat Software: Berkeley DB 4.2.52: (December 3, 2003) - Sleepycat Software: Berkeley DB 4.3.27: (December 22, 2004) + Sleepycat Software: Berkeley DB 4.3.29: (September 6, 2005) + Sleepycat Software: Berkeley DB 4.4.16: (November 12, 2005) Other versions of Berkeley DB between the first and last listed above may or may not work but usually they will. @@ -66,7 +67,7 @@ versions, because the newer can detect data corruptions more reliably (through the use of checksums that detect partially written data base pages); Berkeley DB 4.2 and 4.3 appear a bit faster under load than 4.1 -and older versions. +and older versions, 4.4 has not yet been evaluated. 2.2.1 Upgrading to transactional databases, also from older bogofilter versions @@ -166,11 +167,12 @@ access method), the log file format, or both. You need a "log file upgrade" for your transactional databases if at -least one of these conditions is true: +least one of these conditions is true ("-->" means "to") -- you upgraded Berkeley DB from a 3.X version to a 4.Y version -- you upgraded Berkeley DB from 4.0 or 4.1 to 4.2 or 4.3 -- you upgraded Berkeley DB from 4.2 to 4.3. +- you upgraded Berkeley DB from a 3.X version --> a 4.Y version +- you upgraded Berkeley DB from 4.0 or 4.1 --> 4.2, 4.3 or 4.4 +- you upgraded Berkeley DB from 4.2 --> 4.3 or 4.4 +- you upgraded Berkeley DB from 4.3 --> 4.4 Non-transactional databases do not need log file format upgrades as they do not use log files. @@ -434,7 +436,7 @@ SIZING OPTIONS: - set_cachesize G B C - (valid in Berkeley DB 3.1 - 4.3, requires recovery to change) + (valid in Berkeley DB 3.1 - 4.4, requires recovery to change) sets the cache size to G gigabytes plus B bytes which are spread out in C equally sized caches (all figures are natural numbers). You @@ -448,7 +450,7 @@ will create six caches sized 12500000 bytes (12.5 MB, +25% applied) - set_lg_max 250000 - (valid in Berkeley DB 3.1 - 4.3, takes effect immediately) + (valid in Berkeley DB 3.1 - 4.4, takes effect immediately) this option configures the maximum log file size, in bytes, before Berkeley DB starts a new log file. The default is 1 MB. @@ -456,32 +458,32 @@ SAFE OPTIONS: - set_flags DB_DIRECT_DB - (valid in Berkeley DB 4.1 - 4.3, takes effect immediately) + (valid in Berkeley DB 4.1 - 4.4, takes effect immediately) this option turns off system buffering of *database* files, to avoid double caching of data. NOT SUPPORTED ON ALL PLATFORMS! - set_flags DB_DIRECT_LOG - (valid in Berkeley DB 4.1 - 4.3, takes effect immediately) + (valid in Berkeley DB 4.1 - 4.4, takes effect immediately) this option turns off system buffering of *log* files, to avoid double caching of data. NOT SUPPORTED ON ALL PLATFORMS! - set_flags DB_DSYNC_LOG - (valid in Berkeley DB 4.3, takes effect immediately) + (valid in Berkeley DB 4.3 - 4.4, takes effect immediately) this option can increase performance on some systems (and decrease on other systems), by using the O_DSYNC POSIX flag rather than a separate function to flush the logs. - set_flags DB_NOMMAP - (valid in Berkeley DB 3.2 - 4.3, takes effect immediately) + (valid in Berkeley DB 3.2 - 4.4, takes effect immediately) this option can reduce memory consumption at run time, particularly with large databases, at some cost of performance - set_flags DB_REGION_INIT - (valid in Berkeley DB 3.2 - 4.3, takes effect immediately) + (valid in Berkeley DB 3.2 - 4.4, takes effect immediately) this option causes all shared memory regions to be "page faulted" into core memory at application start and written at data base @@ -492,11 +494,11 @@ - set_verbose DB_VERB_CHKPOINT (valid in Berkeley DB 3.1 - 4.2, takes effect immediately) - set_verbose DB_VERB_DEADLOCK - (valid in Berkeley DB 3.1 - 4.3, takes effect immediately) + (valid in Berkeley DB 3.1 - 4.4, takes effect immediately) - set_verbose DB_VERB_RECOVERY - (valid in Berkeley DB 3.1 - 4.3, takes effect immediately) + (valid in Berkeley DB 3.1 - 4.4, takes effect immediately) - set_verbose DB_VERB_WAITSFOR - (valid in Berkeley DB 3.1 - 4.3, takes effect immediately) + (valid in Berkeley DB 3.1 - 4.4, takes effect immediately) these verbose flags cause extended output for long-lasting operations, ...CHKPOINT prints location information when searching @@ -507,14 +509,14 @@ UNSAFE OPTIONS - these may impair robustness/recoverability of the data base - set_flags DB_TXN_NOSYNC - (valid in Berkeley DB 3.3 - 4.3, takes effect immediately) + (valid in Berkeley DB 3.3 - 4.4, takes effect immediately) if set, the log is not written or synchronously flushed at commit time. In case of an application or system crash, the last few registrations can be lost. - set_flags DB_TXN_WRITE_NOSYNC - (valid in Berkeley DB 4.1 - 4.3, takes effect immediately) + (valid in Berkeley DB 4.1 - 4.4, takes effect immediately) if set, the log is written, but not synchronously flushed at commit time. In case of a system crash, the last few registrations can be @@ -523,15 +525,15 @@ DANGEROUS OPTIONS - these can improve performance, but should be avoided - set_flags DB_TXN_NOT_DURABLE - (valid in Berkeley DB 4.2, takes effect at next application start, - replaced by DB_LOG_INMEMORY for version 4.3) + (valid in Berkeley DB 4.2 - 4.4, takes effect at next application start, + replaced by DB_LOG_INMEMORY for version 4.3 - 4.4) this option prevents writing into log files. In case of application or system crashes, the data base can become corrupt, and large registrations can exhaust the log buffer space and then fail. - set_flags DB_LOG_INMEMORY - (valid in Berkeley DB 4.3, takes effect at next application start) + (valid in Berkeley DB 4.3 - 4.4, takes effect at next application start) this option prevents the writing of any log files to disk. In case of application or system crashes, the data base can become corrupt, and |