bug-coreutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#12366: [gnu-prog-discuss] bug#12366: Writing unwritable files


From: John Darrington
Subject: bug#12366: [gnu-prog-discuss] bug#12366: Writing unwritable files
Date: Thu, 6 Sep 2012 19:17:15 +0000
User-agent: Mutt/1.5.18 (2008-05-17)

On Thu, Sep 06, 2012 at 11:23:21AM -0700, Paul Eggert wrote:
     On 09/06/2012 10:35 AM, Bernhard Voelker wrote:
     > Why can't 'sed -i' be made atomic for the user?
     > Today, it creates a temporary file for the output.
     > At the end, it calls rename(). What if it instead
     > rewinds the input and that temporary file and copies
     > it's content to the input file?
     
     That's kind of what 'sort -o' does, and it also
     has race conditions.  For example, in that last phase
     while it's copying the content to the input file, some other
     process might be reading the input file.

I don't think that matters. In fact I like to be able to use 
tail -f to see what's being written to a file, and find it
the mozilla like behaviour, where I have to wait until the 
entire file is downloaded in order to see the first byte, 
rather annoying.
     
J'

-- 
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://keys.gnupg.net or any PGP keyserver for public key.

Attachment: signature.asc
Description: Digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]