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

List:       kde-devel
Subject:    Re: KConfig and nuking rc files
From:       Lubos Lunak <l.lunak () sh ! cvut ! cz>
Date:       1999-04-18 20:17:37
[Download RAW message or body]

On So, 17 dub 1999, Kurt Granroth wrote :
>Question: What happens with you open a config file with KSimpleConfig
>but NOT with the read-only flag?  Does it do the following?
>
>  Read in the config file and delete it.  Upon flushing or syncing, it writes
>  all the information back to the file file.
Not exactly. Only when syncing, the file is opened with IO_Truncate. The
consequences can be the same, though.
>
>Is this right?  If so, then it might explain why *sometimes* my kbiffrc file
>randomly disappears!  I wonder if KBiff A opens up kbiffrc (and thus deletes
>it).  KBiff B opens up a now empty kbiffrc and can't read in anything.  KBiff
>A writes back the original data but KBiff B writes back an empty file.
>
>Am I way off base, here?  It's hard to test this as it happens so randomly..
>but it *does* happen and that is the only thing I can think of to explain it.
KBiff should simply open kbiffrc read only, it doesn't write anything upon
startup, does it ?
>-- 
>Kurt Granroth
>granroth@kde.org
>http://www.pobox.com/~kurt_granroth

This was mentioned recently, see
http://lists.kde.org/?l=kde-devel&m=92391797222324&w=2

 Lubos Lunak
 l.lunak@email.cz

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