From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/29022] 000-permissions files cause problems for backups
Date: Mon, 04 Apr 2022 21:43:21 +0000 [thread overview]
Message-ID: <bug-29022-10460-wbrqJxtE43@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29022-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29022
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fche at redhat dot com
--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> ---
For what it's worth, these caches are all disposable, so you could exclude the
whole directory structure from backups or just delete it.
I'm not keen on a file-attribute solution, because it's less portable and it'd
still require SOME file to exist. A 0-length file is not unambiguous (consider
empty source files). A differently named file is a possibility.
(Pretty sure atomicity is an orthogonal consideration - TOCTOU is a possibility
with all the options.)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-04-04 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 9:42 [Bug debuginfod/29022] New: " bugzilla at hadess dot net
2022-04-04 21:43 ` fche at redhat dot com [this message]
2022-04-04 22:08 ` [Bug debuginfod/29022] " mark at klomp dot org
2022-04-05 14:36 ` fche at redhat dot com
2022-04-07 11:39 ` mark at klomp dot org
2022-04-13 19:26 ` amerey at redhat dot com
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-29022-10460-wbrqJxtE43@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).