unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: Switching to extindex
Date: Tue, 04 Jun 2024 11:34:03 -0600	[thread overview]
Message-ID: <87sexszk6s.fsf@meer.lwn.net> (raw)
In-Reply-To: <20240604172403.M156885@dcvr>

Eric Wong <e@80x24.org> writes:

> Jonathan Corbet <corbet@lwn.net> wrote:
>> Eric Wong <e@80x24.org> writes:
>> 
>> > Jonathan Corbet <corbet@lwn.net> wrote:
>> >> I"ve run public-inbox-extindex --all and waited a few days; once I
>> >> figured out that I also need to have it running with --watch, things
>> >> *seem* to be working well.
>> >> 
>> >> My understanding is that I can now get rid of the per-inbox indexing and
>> >> get a bunch of disk space back, and I would like to do that.  This,
>> >> though, is the step that I've not been able to figure out.  Which files
>> >> can I remove, and how do I tell public-inbox to not recreate them?
>> >
>> > Yes, you can remove the Xapian shard directories (0, 1, 2, ...)
>> > under xap15 and -watch will be able to detect indexlevel=basic
>> > on the next SIGHUP or restart.
>> 
>> For reasons lost to history, I'm using public-inbox-mda instead; it
>> seems it does not do that detection?  No worries, I can tweak the config
>> file easily enough.
>
> -mda does the detection, too, just every time.  I haven't used
> it much with -extindex but I think it there's tests for it so it works...

Interesting...for me it recreates the 0/1/2 directories unless I edit
the config file explicitly.

Thanks,

jon

  reply	other threads:[~2024-06-04 17:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04 15:59 Switching to extindex Jonathan Corbet
2024-06-04 17:07 ` Eric Wong
2024-06-04 17:18   ` Jonathan Corbet
2024-06-04 17:24     ` Eric Wong
2024-06-04 17:34       ` Jonathan Corbet [this message]
2024-06-04 22:25         ` [PATCH] mda: do not auto-create Xapian indices Eric Wong

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

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sexszk6s.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=e@80x24.org \
    --cc=meta@public-inbox.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 read-only IMAP folder(s) and NNTP newsgroup(s).