[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: ktempfile
From:       Michael Pyne <michael.pyne () kdemail ! net>
Date:       2007-10-18 20:33:17
Message-ID: 200710181633.21179.michael.pyne () kdemail ! net
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Thursday 18 October 2007, Lubos Lunak wrote:
>  BTW, an opinion of two other kernel developers (that don't have any
> specific fs knowledge) is that our response to users complaining about
> losing data this way should be telling them to kiss their data good bye and
> buy UPS or use a filesystem where it works if they don't like it.

Instead of changing KSaveFile or KConfig couldn't we just change 
KBookmarkManager and the KonqHistory code to not use KSaveFile and instead 
just use QFile and rename() (or add a flag to KSaveFile to allow not syncing 
before the rename)?

I don't think the problem is that KSaveFile calls sync() since I'd actually 
almost expect that behavior from its API documentation, but instead that code 
uses KSaveFile where the atomicity/sync guarantee isn't essential.

Regards,
 - Michael Pyne

["signature.asc" (application/pgp-signature)]

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]