From: Chris Wedgwood <cw@f00f.org>
To: Waldo Bastian <bastian@kde.org>
Cc: kde-core-devel@kde.org, Tim Connors <tconnors@astro.swin.edu.au>,
linux-kernel@vger.kernel.org
Subject: Re: kconfig's file handling (was: XFS: how to NOT null files on fsck?)
Date: Tue, 13 Jul 2004 15:28:32 -0700 [thread overview]
Message-ID: <20040713222832.GA7980@taniwha.stupidest.org> (raw)
In-Reply-To: <200407131431.43478.bastian@kde.org>
On Tue, Jul 13, 2004 at 02:31:43PM +0200, Waldo Bastian wrote:
> There is nothing to fix, we already use a tempfile + rename, it's in
> KSaveFile since 1999. Or just look with strace if you don't believe
> me. This Tim Connors guy shouldn't talk about things he obviously
> knows nothing about.
How about fsync on the tempfile before the rename? Without getting
into a religious discussion about whether or not this should be
necessary, it will certainly help in many cases.
> This kind of dataloss is the result of that attitude, either go
> complain with them if it bothers you, or use a filesystem that does
> it right.
I'm not sure people can just change their fs, some people have no
options and for some platforms where KDE is used there might not be
any alternatives. I really think fsync here would help in most if not
all of those cases and it shouldn't adversely affect the performance
(to the best of my knowledge KDE doesn't update dotfiles all that
often and they are pretty small). Other applications do this already
and it seems to be very reliable for them.
--cw
P.S. I'm a bit confused as to why files get smashed on ENOSPC and when
NFS servers croak though.
next prev parent reply other threads:[~2004-07-13 22:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040713110520.GB8930@ugly.local>
2004-07-13 12:31 ` kconfig's file handling (was: XFS: how to NOT null files on fsck?) Waldo Bastian
2004-07-13 12:40 ` Tim Connors
2004-07-13 12:53 ` Oswald Buddenhagen
2004-07-13 21:02 ` Theodore Ts'o
2004-07-13 22:28 ` Chris Wedgwood [this message]
2004-07-14 6:27 Roy Butler
2004-07-14 6:44 ` Chris Wedgwood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040713222832.GA7980@taniwha.stupidest.org \
--to=cw@f00f.org \
--cc=bastian@kde.org \
--cc=kde-core-devel@kde.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tconnors@astro.swin.edu.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.