From: Gabriel Kerneis <gabriel.kerneis@enst.fr>
To: caml-list@yquem.inria.fr
Cc: Ian Zimmerman <itz@madbat.mine.nu>
Subject: Re: [Caml-list] [OT?] spamoracle concurrency
Date: Fri, 13 Apr 2007 08:47:00 +0200 [thread overview]
Message-ID: <20070413084700.7f1b5d8c@kerneis.info> (raw)
In-Reply-To: <87ps68u7ub.fsf@unicorn.ahiker.homeip.net>
[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]
Le 13 Apr 2007 02:06:04 -0400, Ian Zimmerman <itz@madbat.mine.nu> a
écrit :
>
> I couldn't find a forum specifically for spamoracle :-)
>
> 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.
Regards,
--
Gabriel Kerneis
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-04-13 6:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 6:06 Ian Zimmerman
2007-04-13 6:39 ` [Caml-list] " Alain Frisch
2007-04-13 6:56 ` Gabriel Kerneis
2007-04-13 7:57 ` Alain Frisch
2007-04-13 6:47 ` Gabriel Kerneis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070413084700.7f1b5d8c@kerneis.info \
--to=gabriel.kerneis@enst.fr \
--cc=caml-list@yquem.inria.fr \
--cc=itz@madbat.mine.nu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox