Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: marka@pobox.com (Mark Alexander)
Subject: [sup-talk] More about those lost messages
Date: Wed, 8 Apr 2009 10:32:29 -0700	[thread overview]
Message-ID: <a412e2a70904081032x3438abedw3a23d87973f56d35@mail.gmail.com> (raw)

I've been using sup (next branch) for a week or so, and no crashes so
far.  But I'm still having problems with occasional lost messages.
Messages that were definitely in the index in the evening are gone
when I start sup again the next morning.  I've recovered them by doing
a sup-sync --all, but I'm still puzzled by what's going on.

This has happened twice that I've noticed, and in both cases the
message that got lost was part of a thread in which I was
participating, and was in the inbox.  It could be that other messages
got lost in other threads that I was ignoring, but I didn't notice it
because I was ignoring those threads :-) .

When I first noticed this a couple of weeks ago, I thought it might
have something to do with fetchmail running in the background.  I
changed things around so that fetchmail is only running in the
background when sup is not running.  When sup is running, it invokes
fetchmail via the poll hook.  But this doesn't seem to have had any
effect on the lost message problem.

This is just idle, uninformed speculation, but maybe some records that
were in the in-memory index didn't get written to disk when sup
exited?  Would neglecting to use the '$' command do this?


             reply	other threads:[~2009-04-08 17:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08 17:32 Mark Alexander [this message]
2009-04-08 22:34 ` William Morgan
2009-04-09 15:36   ` Mark Alexander

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=a412e2a70904081032x3438abedw3a23d87973f56d35@mail.gmail.com \
    --to=marka@pobox.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