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

List:       kde-devel
Subject:    Re: ktempfile
From:       Thiago Macieira <thiago () kde ! org>
Date:       2007-10-18 15:22:55
Message-ID: 200710181722.55770.thiago () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Em Thursday 18 October 2007 16:07:57 Jaison Lee escreveu:
> If KConfig could me
> be made to sync() in the background this issue goes away. Is someone
> willing to look into this?

Even if you do it in a thread, the whole system syncs. It's not a question of 
whether the GUI is responsive or not -- it's a question of whether there's a 
lot of disk I/O.

In the ideal world, I wouldn't recommend syncing at all: if you have a power 
loss, your data is corrupted and we can't do much about it. But I do remember 
lots of complaints by users in bugs.kde.org about this issue, which is 
probably why the sync was introduced in the first place.

What I don't know is why our config files are more susceptible to corruption 
than other files. Is it the way we save (KSaveFile: write, atomically 
rename)?

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

["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]