Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: marka@pobox.com (Mark Alexander)
Subject: [sup-talk] preparing for 0.7
Date: Thu, 19 Mar 2009 12:18:07 -0700	[thread overview]
Message-ID: <a412e2a70903191218x209c1cb1p6f46e718b2f90395@mail.gmail.com> (raw)
In-Reply-To: <1237383823-sup-8242@entry>

I left the new sup running all night, and when
I looked at it this morning, it had dropped
at least one new message.  I didn't figure that
out until I saw replies to the lost message.
Poking about with mutt and searching for
the message using devel/console.sh showed
that it really was missing from the ferret index.
Running sup-sync --all on the maildir source in question
fixed it, but it was still worrisome.

This is on a work machine that gets messages
from dozens of mailing lists, cron jobs, etc.
I have fetchmail running in the background
and polling every two minutes.  Then procmail
is used to stuff things into a dozen folders
in ~/Maildir (for use with mutt).

So I'm wondering if there is some kind of race
condition between sup and fetchmail/procmail.  I'm not
even sure how to debug this since it's apparently
an infrequent event (and one that isn't noticeable
right away).


  parent reply	other threads:[~2009-03-19 19:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-16 17:27 William Morgan
2009-03-17 18:29 ` Mark Alexander
2009-03-18 13:49   ` William Morgan
2009-03-18 15:39     ` Lee Hinman
2009-03-19 17:02       ` William Morgan
2009-03-18 21:11     ` Mark Alexander
2009-03-19 19:18     ` Mark Alexander [this message]
2009-03-19 19:25       ` William Morgan
2009-03-19 20:41         ` Mark Alexander
2009-04-15 17:29           ` [sup-talk] Lost Maildir Messages Iain

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=a412e2a70903191218x209c1cb1p6f46e718b2f90395@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