From 9d0f13c4c054c622676d40f4574cb7abb916bcb4 Mon Sep 17 00:00:00 2001 From: Alexander Neumann Date: Sun, 3 Dec 2017 19:12:07 +0100 Subject: [PATCH] Prominently mention SIGPIPE issue in CHANGELOG --- CHANGELOG.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 78cf386e8..49051fd96 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,6 +4,13 @@ released version of restic from the perspective of the user. Important Changes in 0.X.Y ========================== + * We've disabled handling SIGPIPE again. Turns out, writing to broken TCP + connections also raised SIGPIPE, so restic exits on the first write to a + broken connection. Instead, restic should retry the request. + https://github.com/restic/restic/pull/1459 + https://github.com/restic/restic/issues/1457 + https://github.com/restic/restic/issues/1466 + Small changes ------------- @@ -26,8 +33,7 @@ Small changes `--with-atime` to the `backup` command. https://github.com/restic/restic/pull/1452 - * We've improved the s3 backend to work with DigitalOcean Spaces. In addition, - handling of SIGPIPE was removed. + * We've improved the s3 backend to work with DigitalOcean Spaces. https://github.com/restic/restic/pull/1459 https://github.com/restic/restic/issues/1457