[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Wed, 13 Mar 2024 09:28:07 +0100
From: Florian Weimer <fweimer@...hat.com>
To: "Zack Weinberg" <zack@...folio.org>
Cc: "Rich Felker" <dalias@...c.org>, "Gabriel Ravier"
<gabravier@...il.com>, "Skyler Ferrante (RIT Student)" <sjf5462@....edu>,
musl@...ts.openwall.com, "Andreas Schwab" <schwab@...e.de>, "Alejandro
Colomar" <alx@...nel.org>, "Thorsten Glaser" <tg@...bsd.de>, NRK
<nrk@...root.org>, "Guillem Jover" <guillem@...rons.org>, "GNU libc
development" <libc-alpha@...rceware.org>, libbsd@...ts.freedesktop.org,
"Serge E. Hallyn" <serge@...lyn.com>, "Iker Pedrosa"
<ipedrosa@...hat.com>, "Christian Brauner" <christian@...uner.io>
Subject: Re: Re: Tweaking the program name for <err.h> functions
* Zack Weinberg:
> I do fully agree that this is a design error in NFS and in close(2)
> more generally [like all destructors, it should be _impossible_ for
> close to fail], but there is no realistic prospect of changing it, and
> I've been burned a few times by programs that didn't notice delayed
> write errors.
There is fsync to avoid delayed write errors. Historically, it's been
very bad for performance. What coreutils et al. aim to do is to deal
with non-catastrophic failures (mainly out of space errors) without
incurring the fsync overhead.
Thanks,
Florian
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
