<br><br><div><span class="gmail_quote">On 10/10/07, <b class="gmail_sendername">David Faure</b> <<a href="mailto:faure@kde.org">faure@kde.org</a>> wrote:</span><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wednesday 10 October 2007, Thomas Braxton wrote:<br>> On 10/9/07, Nhuh Put <<a href="mailto:nhuh.put@web.de">nhuh.put@web.de</a>> wrote:<br>> ><br>> > Von: Thomas Braxton<br>> > Gesendet: Dienstag, 9. Oktober 2007 21:22
<br>> > An: <a href="mailto:kde-core-devel@kde.org">kde-core-devel@kde.org</a><br>> > Betreff: Re: KConfig/KLockFile performance (was KMimeType performance)<br>> ><br>> > > On 10/9/07, David Faure <
<a href="mailto:faure@kde.org">faure@kde.org</a>> wrote:<br>> > > On Tuesday 09 October 2007, Maksim Orlovich wrote:<br>> > > > KDesktopFile/KConfig tries to lock the file with KLockFile<br>> > >
<br>> > > Huh. I thought we got rid of the "bool readonly" because it made no<br>> > behavior difference,<br>> > > but if KConfig locks the file then surely we need a "ReadOnly" flag
<br>> > again?<br>> > > Or better: we should lock at the time of writing to the file, not when<br>> > just reading from it!<br>> > ><br>> > > your mail came in as I was sending the last patch, here's another try.
<br>> > this time only locking in sync() and only if the file is read-write.<br>> ><br>> > This should work, but there is one problem: configState is only set to<br>> > ReadOnly in<br>> > KConfig::isConfigWritable, which is normally not called, so there should
<br>> > probably be<br>> > a call to it in KConfigPrivate::changeFileName, or this will not have much<br>> > effect.<br>><br>><br>> I thought I already made that change, I must have forgot to commit it,
<br>> probably when I was having trouble getting a good update and had to get a<br>> clean checkout<br><br>I'm not sure what the current status is supposed to be (any uncommitted patch?),<br>but I still see a lot of lock files created (or trying to be), both in /usr (no permissions) and in
<br>user-writable dirs (the lock file -can- be created, but why should it be, if we're only reading the file?)</blockquote><div><br class="webkit-block-placeholder"></div><div>sorry, didn't have time to commit yesterday, committed now.
</div><div><br class="webkit-block-placeholder"></div><div>Thomas</div><div><br class="webkit-block-placeholder"></div></div>