Version française
Home     About     Download     Resources     Contact us    
Browse thread
[OT?] spamoracle concurrency
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: Gabriel Kerneis <gabriel.kerneis@e...>
Subject: Re: [Caml-list] [OT?] spamoracle concurrency
--Sig_YkwRcdBxY.CMEVl0oJ7T0Ax
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Le 13 Apr 2007 02:06:04 -0400, Ian Zimmerman <itz@madbat.mine.nu> a
=E9crit :
>=20
> I couldn't find a forum specifically for spamoracle :-)
>=20
> The question is: does spamoracle do any kind of locking on the
> database? And what kind?  Clearly, if I pipe my mails through
> "spamoracle mark" in my procmail (or maildrop, etc.) configuration,
> spamoracle may run and access the database at completely
> unpredictable times.  Is it safe to do "spamoracle add" while this is
> enabled?  Or do I have to slap a locking scheme on top myself?

After a quick glance at the source code of spamoracle 1.4 (that I used
a few years ago for a school project), I would answer "no" : database
is read from file to memory, and if you do "spamoracle add", it will
update the database (in memory), then dump it back to a (temporary)
file which will eventually being renamed and erase your previous
database. As far as I can see, there is no locking of any kind.
But if you process your mails one by one, there shouldn't be any
problem either ; it depends on your MDA.=20

Regards,
--=20
Gabriel Kerneis


--Sig_YkwRcdBxY.CMEVl0oJ7T0Ax
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGHydr6a2JmXQu5bYRAssBAKC6ITgP9K1BDluXAMp9EMpLF3bL1ACdFJpc
FCuT4M62bxaD+aKgC64K4vs=
=D2vp
-----END PGP SIGNATURE-----

--Sig_YkwRcdBxY.CMEVl0oJ7T0Ax--