hi,
~~~ s...@datanet.hu írta: ~~~
sqlite3 version... It's an administrative nightmare having different
versions of the same lib on
Indeed, you are right. Generally I try to keep up with the latest
releases
of the used database software versions, and I think it is a good thing. I
from a perspective of a developer, you're perfectly right (no upstream
problems, uptodate bugfixes and improvements are incorporated right into
clapf etc.) From a perspective of a sysadmin, it's hard to maintain a system
with fresh -release software, most distro's lifetime is 3-5 years.
Unfortunately I cannot find the 3.3.8 version of sqlite3. So if you want,
I may create a statically linked binary package for you (against sqlite3
v3.5.6).
that's very kind, thanks! But even better, what about putting some words
into the doc about how one can get the latest sqlite and link clapf
statically to it? By this, no other app could find the new sqlite (it can be
removed after make) and clapf can use it happily, too. I mean some
--with-sqlite3=/foo/bar switch which can be used to point the clapf
configure script to the downloaded sqlite sources.
a system, so i'd rather avoid it, if possible. Also, i don't want to tie
the spam filtering service to the sql service, for reliability reasons
(if the db is shut down for maintenance or dies, then emails are held up
or get bounced or lost) that's why i insist on sqlite for my setup.
That's not the case with clapf. If it cannot connect to the mysql server,
it will timeout its connection (see the mysql_connect_timeout variable in
clapf.conf), and return with 0.5 as the message spamicity.
My bad, i simply overlooked it :( But i still don't want to tie email and
database service....
Please note that the mysql server may perform better in a large
Yes i've read your posts in HUP and at your site.
environment than sqlite3. It depends on your setup.
i'm going to do a per-user sqlite file + maildrop combo, then we see the
results
And an another question: how can mysql be disabled upon configure (make
configure report "MySQL support: no" at the end)?
I will release the 0.3.30 final version soon, and it will not contain that
i hardly can wait!
"unnecessary" mysql check.
so mysql support is not compiled in totally when sqlite is selected as a
token database?
thanks for the answers!
----
Péter
Serial is up, protocol is up --- everything connected!
(c) Anthony Panda www.anthonypanda.com
PS: is there a mailing list archive? I wasn't able to find one....
P
