Bug#607267: /usr/bin/scp: fails to notice close() errors
On Mon, Dec 05, 2011 at 05:03:25PM +0100, Michal Suchanek wrote:
> Excerpts from Helmut Grohne's message of Mon Dec 05 15:54:19 +0100 2011:
> > Can we now ignore 2) and concentrate on 1)?
> No. If I wanted this semantics I could use shred(1).
Please report a separate bug about not using fsync then. (or clone this
bug) They can be fixed independently.
> I want my files saved.
Honestly. You seem to have a rather different view on this issue than
the rest of the world (otherwise it would have been reported way
As for me I really do *not* want fsync here. For instance when I use a
slow usb storage device, I really want cp to finish before the copied
stuff is written to permanent storage.
So even I would assume that the fsync issue is just wontfix (even though
I am not the openssh maintainer).
> Note that this same issue has been found and fixed in dpkg.
This is good and all. But in general tools simply do not provide fsync
semantics and people actually expect that now. When firefox tried to
introduce fsync, it was disabled for performance reasons again. If you
need it, go sync after you copy. (Or write patches.)