From 25f4acdaa85324b650441b5b75c45af9835818af Mon Sep 17 00:00:00 2001 From: Michael Eischer Date: Tue, 29 Dec 2020 16:03:01 +0100 Subject: [PATCH] Add changelog entry --- changelog/unreleased/issue-2706 | 16 ++++++++++++++++ doc/manual_rest.rst | 3 +++ 2 files changed, 19 insertions(+) create mode 100644 changelog/unreleased/issue-2706 diff --git a/changelog/unreleased/issue-2706 b/changelog/unreleased/issue-2706 new file mode 100644 index 000000000..286675a87 --- /dev/null +++ b/changelog/unreleased/issue-2706 @@ -0,0 +1,16 @@ +Enhancement: Configurable progress reports for non-interactive terminals + +The `backup`, `check` and `prune` commands never printed any progress +reports on non-interactive terminals. This behavior is now configurable +using the `RESTIC_PROGRESS_FPS` environment variable. Use for example a +value of `1` for an update per second or `0.01666` for an update per minute. + +The `backup` command now also prints the current progress when restic +receives a `SIGUSR1` signal. + +Setting the `RESTIC_PROGRESS_FPS` environment variable or sending a `SIGUSR1` +signal prints a status report even when `--quiet` was specified. + +https://github.com/restic/restic/issues/2706 +https://github.com/restic/restic/issues/3194 +https://github.com/restic/restic/pull/3199 diff --git a/doc/manual_rest.rst b/doc/manual_rest.rst index d8167fb4a..0f2ff5e06 100644 --- a/doc/manual_rest.rst +++ b/doc/manual_rest.rst @@ -145,6 +145,9 @@ Additionally, on Unix systems if ``restic`` receives a SIGUSR1 signal the current progress will be written to the standard output so you can check up on the status at will. +Setting the `RESTIC_PROGRESS_FPS` environment variable or sending a `SIGUSR1` +signal prints a status report even when `--quiet` was specified. + Manage tags -----------