From: Ian Zimmerman <itz@madbat.mine.nu>
To: caml-list@yquem.inria.fr
Subject: [OT?] spamoracle concurrency
Date: 13 Apr 2007 02:06:04 -0400 [thread overview]
Message-ID: <87ps68u7ub.fsf@unicorn.ahiker.homeip.net> (raw)
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?
Bonus question, if locking is in fact done, does it let multiple
"spamoracle mark" processes through at the same time (which should be safe)?
I found to my dismay that none of the ~5 bayesian type filters I tried
today answers these (obvious?) questions in their documentation :-(
--
Experience with Asset Control an asset.
next reply other threads:[~2007-04-13 6:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 6:06 Ian Zimmerman [this message]
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
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=87ps68u7ub.fsf@unicorn.ahiker.homeip.net \
--to=itz@madbat.mine.nu \
--cc=caml-list@yquem.inria.fr \
/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