From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/28430] New: debuginfod should support a read-only database mode
Date: Wed, 06 Oct 2021 18:08:21 +0000 [thread overview]
Message-ID: <bug-28430-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28430
Bug ID: 28430
Summary: debuginfod should support a read-only database mode
Product: elfutils
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: debuginfod
Assignee: unassigned at sourceware dot org
Reporter: fche at redhat dot com
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
For purposes of scaling workers against a shared database, this sort of thing
should work:
debuginfod -d 'file:///PATH?mode=ro' -R -Z ..
which would force read-only operation. (Presumably, the PATH represents a
database that some other debuginfod is populating/grooming.)
It could be enough to have a flag that suppresses startup-time DDL application,
grooming, traversal, and scanning, leaving only the libmicrohttpd-related
threads.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-10-06 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 18:08 fche at redhat dot com [this message]
2021-11-11 15:08 ` [Bug debuginfod/28430] " mark at klomp dot org
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=bug-28430-10460@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.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).