From: Romain Dessort <romain@univers-libre.net>
To: Thorsten Fischer <thorsten@net.t-labs.tu-berlin.de>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Delete email from Sup index
Date: Fri, 11 Feb 2011 19:36:32 +0100 [thread overview]
Message-ID: <1297448359-sup-6036@mail.univers-libre.net> (raw)
In-Reply-To: <1297433878-sup-5263@mail.froschi.org>
Excerpts from Thorsten Fischer's message of ven fév 11 15:25:01 +0100 2011:
> I have been through exactly that about ten minutes ago to get rid of
> >40k index entries in my sup setup. Good timing! ;)
Yeah, but I receive too much cron output emails and other boring
automatic daily reports, so it's easy to reach this value ;).
> What I did:
>
> * stopped the periodic polling of my offlineimap, just in case, to keep
> the sources from changing.
> * made a backup of my .sup/ folder, just in case.
> * created a label dump file using sup-dump.
> * deleted the .sup/xapian folder.
> * run sup-sync with the --restore option, pointing to the dump file.
>
> The index was re-created from the dump file, but only taking into
> account the files that were currently available from the sources. Worked
> like a charm. Better, in fact, since charms don't work at all. Ahem.
Ok, this should be a good hack if I do this operation occasionally, but
I can hardly automated it…
But thank you anyway!
--
Romain Dessort
Jabber ID : romain@univers-libre.net
GnuPG : 3072D/724BC532
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2011-02-11 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 13:08 Romain Dessort
2011-02-11 14:25 ` Thorsten Fischer
2011-02-11 18:36 ` Romain Dessort [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=1297448359-sup-6036@mail.univers-libre.net \
--to=romain@univers-libre.net \
--cc=sup-talk@rubyforge.org \
--cc=thorsten@net.t-labs.tu-berlin.de \
/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