From: "Ted Zlatanov" <tzz@lifelogs.com>
Subject: Re: Don't wait for sa-learn
Date: 20 Mar 2006 16:43:50 -0500 [thread overview]
Message-ID: <4nveu8eqqx.fsf@asimov.bwh.harvard.edu> (raw)
In-Reply-To: <87pskgerpf.fsf@freemail.hu> (Magnus Henoch's message of "Mon, 20 Mar 2006 22:23:08 +0100")
On 20 Mar 2006, mange@freemail.hu wrote:
> "Ted Zlatanov" <tzz@lifelogs.com> writes:
>
>> I don't know if this is a good idea. If you submit multiple jobs at
>> once, does sa-learn do the right thing? I use a version heavily
>> customized by my ISP, so I don't know if the vanilla SpamAssassin will
>> work.
>
> Some source diving tells me that it tries to acquire a lock on the
> file, and fails after ten retries (one second between each), so it
> should be safe.
That seems like a bad situation to me, because the sa-learn run has
the potential to fail silently if the first run is longer than 10
seconds. Maybe we need to set up a job queue. That may be hard to
implement, although it will be generally useful.
I'm OK with adding a variable instead, spam-train-in-background, which
is nil by default but can be turned on for specific backends.
Any opinions?
Ted
prev parent reply other threads:[~2006-03-20 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-18 13:40 Magnus Henoch
2006-03-20 19:57 ` Ted Zlatanov
2006-03-20 21:23 ` Magnus Henoch
2006-03-20 21:43 ` Ted Zlatanov [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=4nveu8eqqx.fsf@asimov.bwh.harvard.edu \
--to=tzz@lifelogs.com \
/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;
as well as URLs for NNTP newsgroup(s).