From: Eric Wong <e@80x24.org>
To: "Robin H. Johnson" <robbat2@gentoo.org>
Cc: meta@public-inbox.org, infra@gentoo.org
Subject: Re: public-inbox skipping new inboxes or many mails
Date: Wed, 17 Jul 2024 23:50:17 +0000 [thread overview]
Message-ID: <20240717235017.M975178@dcvr> (raw)
In-Reply-To: <20240717232532.M125694@dcvr>
> "Robin H. Johnson" <robbat2@gentoo.org> wrote:
> > I hacked in stderr: but bad luck, it doesn't dump anything useful before
> > it seems to vanish. Nothing in dmesg either, so a mundane crash.
Actually, did it say "# scanning" anywhere at startup?
There's already a diagnostic message that's been there a while
(but not scan completion)
Similarly, SIGHUP should already emit "# reloaded" to stderr.
next prev parent reply other threads:[~2024-07-17 23:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 6:15 public-inbox skipping new inboxes or many mails Robin H. Johnson
2024-07-15 21:03 ` Eric Wong
2024-07-15 21:45 ` Robin H. Johnson
2024-07-15 23:58 ` Eric Wong
2024-07-16 5:45 ` Robin H. Johnson
2024-07-16 19:05 ` Eric Wong
2024-07-17 3:04 ` Robin H. Johnson
2024-07-17 23:25 ` Eric Wong
2024-07-17 23:50 ` Eric Wong [this message]
2024-07-18 0:02 ` Robin H. Johnson
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=20240717235017.M975178@dcvr \
--to=e@80x24.org \
--cc=infra@gentoo.org \
--cc=meta@public-inbox.org \
--cc=robbat2@gentoo.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).