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

List:       kde-devel
Subject:    Re: ktempfile
From:       Adam Pigg <piggz1 () gmail ! com>
Date:       2007-10-17 9:25:00
Message-ID: 200710170925.01803.adam () piggz ! co ! uk
[Download RAW message or body]

On Wednesday 17 October 2007 07:54:58 Thiago Macieira wrote:
> Em Wednesday 17 October 2007 01:50:22 Michael Pyne escreveu:
> > #0  KTempFile::sync (this=0x7ffffe5213a8)
> >     at /home/kde-svn/kdesvn/kdelibs/kdecore/ktempfile.cpp:216
> > #1  0x00002ba8adbf5274 in KSaveFile::close (this=0x7ffffe5213a0)
> >     at /home/kde-svn/kdesvn/kdelibs/kdecore/ksavefile.cpp:111
>
> KSaveFile always calls sync to make sure that the data is written to disk.
>
> It's either that or live with all those emails about "my config got
> corrupted when the power went out".

Perhaps an option:
*Optimise for speed
*Optimise for stability

It sounds quite like how you mount usb sticks, you can mount it 'sync' so that 
you can pull it out (more) safely, but takes longer to write, or without the 
sync option so that writes 'seem' faster, but you have to remember to eject 
it etc first

-- 
Piggz - http://www.piggz.co.uk
Linux enterprise.my.net 2.6.22.9-1mdvcustom #2 SMP PREEMPT Sat Sep 29 08:28:58 
UTC 2007 i686 Intel(R) Celeron(R) M processor         1.50GHz GNU/Linux
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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