[cvs] bogofilter AUTHORS,1.22,1.23 NEWS,1.295,1.296 README,1.16,1.17 TODO,1.13,1.14 configure.ac,1.3
Fast Bayesian spam filter along lines suggested by Paul Graham
Brought to you by:
m-a
From: <m-...@us...> - 2004-10-29 01:12:01
|
Update of /cvsroot/bogofilter/bogofilter In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv29084 Modified Files: AUTHORS NEWS README TODO configure.ac Log Message: Merge Transactional Store from branch. Index: AUTHORS =================================================================== RCS file: /cvsroot/bogofilter/bogofilter/AUTHORS,v retrieving revision 1.22 retrieving revision 1.23 diff -u -d -r1.22 -r1.23 --- AUTHORS 29 Jun 2004 15:51:39 -0000 1.22 +++ AUTHORS 29 Oct 2004 01:11:52 -0000 1.23 @@ -28,5 +28,6 @@ Dan Deward Burkhard Kaas Henning Makholm -Charles A Edwards +Charles A. Edwards Pablo Rosciani +Pavel Kankovsky Index: NEWS =================================================================== RCS file: /cvsroot/bogofilter/bogofilter/NEWS,v retrieving revision 1.295 retrieving revision 1.296 diff -u -d -r1.295 -r1.296 --- NEWS 26 Oct 2004 00:04:41 -0000 1.295 +++ NEWS 29 Oct 2004 01:11:52 -0000 1.296 @@ -5,6 +5,10 @@ NOTE: More information on important changes for bogofilter updaters is in the RELEASE.NOTES files. Read them!! + 2004-10-28 + + * Merged Transactional branch (for BerkeleyDB) back into the trunk. + 2004-10-25 * Added GETTING.STARTED document. @@ -74,6 +78,16 @@ * Fixed help messages for bogofilter's "-m" and "-o" options. + 2004-09-21 + * bogofilter can now be used with Berkeley DB 3.0 or 3.1 although this + is not recommended. You should prefer 4.2 or 4.1 instead. + * Documentation on the write cache issue (recoverability of data bases) + has been revised. + + 2004-09-13 + * Updates doc/README.db with a section on the log file size and + pointers to db_checkpoint and db_archive. + 2004-09-10 * bogofilter-tuning.HOWTO revised and converted to html. @@ -82,6 +96,37 @@ * Ensure that robx computation uses a regular wordlist (rather than an ignore list) to avoid a seg fault in bogotune. + + 2004-09-03 (txn 2.1) + * The on-line crash detector would consider its own process a zombie, + so all processes that lasted 30 s or longer would abort themselves + after that period. + + This was particularly prominent with BerkeleyDB 4.1 with + x86/gcc-assembly mutexes as this combination appears rather slow when + facing lock contention, causing t.lock3 failure. BDB 4.1 compiled to + use POSIX mutexes (where working) appears to be a lot faster in this + situation. + + 2004-09-01 (txn 2.0) + * Hook up crash detection code. Bogofilter is now able to detect + when recovery is necessary and should detect stalled data bases + within 30 seconds. + NOTE: this means if one process crashes all other processes + accessing the same data base will abort with an error code. + + Stalled data bases happen when one process or the system crashes and + doesn't have a chance to clear its locks. + + This code uses ideas from Matthias Andree and Pavel Kankovsky. + + 2004-08-23 (txn 1.1) + * Add -f and -F options to bogoutil (mnemonic: fix) to run data base + recovery. + * Reimplement our own locking so that recovery and data base access + don't collide and no two processes try running recovery at the same + time. + 2004-08-30 * Remove bogus 'P' in bogolexer's allowed option list. Index: README =================================================================== RCS file: /cvsroot/bogofilter/bogofilter/README,v retrieving revision 1.16 retrieving revision 1.17 diff -u -d -r1.16 -r1.17 --- README 26 Oct 2004 00:03:05 -0000 1.16 +++ README 29 Oct 2004 01:11:52 -0000 1.17 @@ -4,6 +4,7 @@ Summary: +0. Important 1. What is Bogofilter? 2. Documentation 3. Installing Bogofilter @@ -16,6 +17,19 @@ d. Changing Bogofilter +0. IMPORTANT +------------ + +If you are using bogofilter with the Berkeley DB data base library +(which is the default, received most testing, is the most powerful of +the data base engines that bogofilter supports and hence recommended), +do read the doc/README.db file, it contains important information. + +The doc/README.db file contains troubleshooting information and +requirements that should be read ahead of time so you can fix problems +quickly should they arise later. + + 1. What is Bogofilter? ---------------------- @@ -84,7 +98,7 @@ sending a message to bog...@bo... and responding to the confirmation message it sends to you. More information is available on the bogofilter home page at -http://bogofilter.sourceforge.net +http://bogofilter.sourceforge.net/ Bugs can be reported via the bogfilter mailing list or through http://sourceforge.net/tracker/?atid=499997&group_id=62265&func=browse @@ -111,7 +125,7 @@ a. Downloading -------------- - The most recent version of this software is available at: + The most recent version of this software is available at: http://sourceforge.net/projects/bogofilter/ Index: TODO =================================================================== RCS file: /cvsroot/bogofilter/bogofilter/TODO,v retrieving revision 1.13 retrieving revision 1.14 diff -u -d -r1.13 -r1.14 --- TODO 13 Apr 2004 00:15:36 -0000 1.13 +++ TODO 29 Oct 2004 01:11:52 -0000 1.14 @@ -2,6 +2,10 @@ bogofilter TODO list +**** Print warning when TDB/QDBM attempt recovery. + +**** Make sure that RFC-2047 decoder runs only once, not recursively. + **** New Feature: Token aging. Support for struct data in the wordlists is already present. Index: configure.ac =================================================================== RCS file: /cvsroot/bogofilter/bogofilter/configure.ac,v retrieving revision 1.303 retrieving revision 1.304 diff -u -d -r1.303 -r1.304 --- configure.ac 20 Oct 2004 00:57:28 -0000 1.303 +++ configure.ac 29 Oct 2004 01:11:52 -0000 1.304 @@ -1,6 +1,6 @@ # $Id$ dnl vim: set noai tw=0: -AC_INIT(bogofilter, 0.92.8.cvs) +AC_INIT(bogofilter, 0.92.99.cvs) AC_PREREQ(2.54) AC_CONFIG_SRCDIR([src/bogofilter.c]) AC_CANONICAL_TARGET @@ -153,12 +153,19 @@ dnl Checks for libraries. AC_CHECK_LIB([m], [cos]) +dnl fdatasync can be faster than fsync but may be in librt on some systems +dnl such as Solaris. The code is currently stubbed out in db_lock.c +dnl AC_SEARCH_LIBS([fdatasync],[rt],AC_DEFINE(HAVE_FDATASYNC,1,[Define to 1 if you have the 'fdatasync' function.])) + AC_CHECK_DECLS([getopt,optreset],,,[[ #include <unistd.h> /* Solaris */ #include <stdlib.h> ]]) +dnl check for SYNC stuff +AC_CHECK_DECLS([O_DSYNC, O_SYNC, O_FSYNC],,,[#include <fcntl.h>]) + dnl Coerce GLIBC 2.3 to GLIBC 2.2 compatibility. dnl May not be complete with future extensions, but appears to work dnl today, 2003-10-02. Matthias Andree |