summaryrefslogtreecommitdiff
path: root/doc/ChangeLog
diff options
context:
space:
mode:
authorNoah Sanci <nsanci@redhat.com>2021-07-26 13:29:11 -0400
committerMark Wielaard <mark@klomp.org>2021-08-04 15:23:15 +0200
commit72a6f9d6f4280a50631b475e620f9c7858d9f4b5 (patch)
treed8e32ff5ebd795a4754913eece63c86febe919f2 /doc/ChangeLog
parent216996bc7b343e84997af364bbe135f02b14fa59 (diff)
downloadelfutils-72a6f9d6f4280a50631b475e620f9c7858d9f4b5.tar.gz
debuginfod: PR27982 - added DEBUGINFOD_MAXSIZE and DEBUGINFOD_MAXTIME
DEBUGINFOD_TIMEOUT is a good way to catch servers that are too slow to *start* transmitting a file. But we have no way of limiting total download time or space. A user might prefer to have his debugger fetch only quick & small files, and make do without the bigger ones. Some transitive dependencies of e.g. gnome programs are huge: 3GB of LLVM debuginfo, 1GB of webkitgtk, etc. etc. DEBUGINFOD_MAXSIZE and DEBUGINFOD_MAXTIME were added to dictate the max download size and time of a debuginfod client. DEBUGINFOD_MAXSIZE is handled server-side and is sent using the http header: X-DEBUGINFOD-MAXSIZE. The client side then checks to ensure this maxsize has been respected. https://sourceware.org/bugzilla/show_bug.cgi?id=27982 Signed-off-by: Noah Sanci <nsanci@redhat.com>
Diffstat (limited to 'doc/ChangeLog')
-rw-r--r--doc/ChangeLog6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/ChangeLog b/doc/ChangeLog
index 05fcd23d..1822fc6b 100644
--- a/doc/ChangeLog
+++ b/doc/ChangeLog
@@ -1,3 +1,9 @@
+2021-07-26 Noah Sanci <nsanci@redhat.com>
+
+ PR27982
+ * debuginfod-find.1: Document DEBUGINFOD_MAXTIME
+ and DEBUGINFOD_MAXSIZE.
+
2021-04-23 Frank Ch. Eigler <fche@redhat.com>
PR27701