summaryrefslogtreecommitdiffstats
path: root/usr.bin
diff options
context:
space:
mode:
authorkientzle <kientzle@FreeBSD.org>2007-02-18 06:23:57 +0000
committerkientzle <kientzle@FreeBSD.org>2007-02-18 06:23:57 +0000
commitf9b1e90cfbd1658706df64b4a2b58d1f7deea4b1 (patch)
treebf0b944e83d3282c20b25214f14bf7d156fc8540 /usr.bin
parentc0ed1b65cf97d4a558e1277b708beebf95b6516d (diff)
downloadFreeBSD-src-f9b1e90cfbd1658706df64b4a2b58d1f7deea4b1.zip
FreeBSD-src-f9b1e90cfbd1658706df64b4a2b58d1f7deea4b1.tar.gz
Andrew and Colin each pointed out to me that truncating the backup
of a growing file should not be considered a "bad thing." PR: bin/108990 MFC after: 7 days Pointy hat: /me
Diffstat (limited to 'usr.bin')
-rw-r--r--usr.bin/tar/write.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/usr.bin/tar/write.c b/usr.bin/tar/write.c
index d7fbcfb..255074c 100644
--- a/usr.bin/tar/write.c
+++ b/usr.bin/tar/write.c
@@ -860,8 +860,6 @@ write_file_data(struct bsdtar *bsdtar, struct archive *a, int fd)
/* Write was truncated; warn but continue. */
bsdtar_warnc(bsdtar, 0,
"Truncated write; file may have grown while being archived.");
- /* Make bsdtar return a final error because of this. */
- bsdtar->return_value = 1;
return (0);
}
bytes_read = read(fd, buff, sizeof(buff));
OpenPOWER on IntegriCloud