From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Gnus registry upgrade didn't import old registry
Date: Wed, 28 Sep 2011 19:37:13 -0500 [thread overview]
Message-ID: <874nzwnpza.fsf@lifelogs.com> (raw)
In-Reply-To: <87mxdp1j53.fsf@uwo.ca>
On Tue, 27 Sep 2011 22:43:36 -0400 Dan Christensen <jdc@uwo.ca> wrote:
DC> Ted Zlatanov <tzz@lifelogs.com> writes:
>> Could you look at what the following produces? This should simulate
>> the candidates that `registry-prune' gets:
>>
>> (let* ((db gnus-registry-db)
>> (hs (oref db :max-hard))
>> (ss (oref db :max-soft)))
>> (oset db :max-hard 10000)
>> (oset db :max-soft most-positive-fixnum)
>> (prog1 (list (registry-prune-soft-candidates db)
>> (registry-prune-hard-candidates db))
>> (oset db :max-hard hs)
>> (oset db :max-soft ss)))
DC> The output is long and is shown with ...:
DC> ((536870911 (nil "<20110913120207.7B6336142@lwahl>"
DC> "fake+none+nndraft:drafts+1" "fake+none+nndraft:drafts+2"
DC> "<73b0a166382dc.4e6e5c38@uwo.ca>"
DC> "<1315880651.2311.22.camel@mike-desktop>"
DC> "<4E6F239E.8030506@gmail.com>" "<4E6EAF23.1070406@uwo.ca>"
DC> "<LYRIS-60085979-25089418-2011.09.13-02.55.25--jdc#uwo.ca@go.netatlantic.com>"
DC> "<2139667233.835036.1315899248272.JavaMail.app@ela4-bed46.prod>"
DC> "<4E6F60C1.7090809@wagnerrp.com>"
DC> "<p062408a2ca951193efe9@simon.thehobsons.co.uk>" ...)) (8997.2 nil))
DC> But there's a lot in that sub-list starting with nil:
DC> (length (cadar result))
DC> 10028
Hmmmm. I'll think about it, nothing obvious so far. Sorry.
DC> Could it be that during the import-eld process, pruning doesn't take
DC> place?
Right.
DC> But why then was I still getting errors when new mail was arriving?
DC> (And could those be reduced to warnings, so that one can still
DC> receive mail when a problem occurs?)
I think the hard limit was not adjusted somehow (maybe because of the
abort). Could you please look at
(let* ((db gnus-registry-db)
(list (oref db :max-hard)) (oref db :max-soft)))
and see if it's 100K or 10K for the hard limit (and what's the soft
limit).
I haven't seen your data files yet, perhaps my spam filter ate them.
I'll look again. They should help me duplicate the problem.
Thanks!
Ted
next prev parent reply other threads:[~2011-09-29 0:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 14:59 Dan Christensen
2011-09-26 20:25 ` Ted Zlatanov
2011-09-26 20:37 ` Dan Christensen
2011-09-26 20:50 ` Dan Christensen
2011-09-26 22:02 ` Ted Zlatanov
2011-09-27 2:12 ` Dan Christensen
2011-09-27 2:35 ` Dan Christensen
2011-09-27 21:25 ` Ted Zlatanov
2011-09-28 2:43 ` Dan Christensen
2011-09-29 0:37 ` Ted Zlatanov [this message]
2011-09-27 10:42 ` Ted Zlatanov
2011-09-26 20:41 ` Dan Christensen
2011-09-26 21:57 ` Ted Zlatanov
2011-09-27 2:07 ` Dan Christensen
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=874nzwnpza.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
/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).