[musl] Re: Tweaking the program name for <err.h> functions

[Florian Weimer]

* 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