[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Why does close_stdout close stdout and stderr?
|
From: |
Bruno Haible |
|
Subject: |
Re: Why does close_stdout close stdout and stderr? |
|
Date: |
Tue, 07 May 2019 00:32:52 +0200 |
|
User-agent: |
KMail/5.1.3 (Linux/4.4.0-145-generic; KDE/5.18.0; x86_64; ; ) |
Florian Weimer wrote:
> ... would be fsync. And I doubt you want to
> call that, purely for performance reasons.
The trade-off between data safety and speed of disk accesses
is to be done by the system administrator, when they decide whether
to use the mount option 'sync' or not. It would be wrong for gnulib
to call fsync() in close_stdout, because that would force the
safety and inefficiency of immediate syncing on systems which have
not asked for it.
Bruno
Re: Why does close_stdout close stdout and stderr?, Paul Eggert, 2019/05/06
Re: Why does close_stdout close stdout and stderr?,
Bruno Haible <=
- Re: Why does close_stdout close stdout and stderr?, Assaf Gordon, 2019/05/07
- Re: Why does close_stdout close stdout and stderr?, Assaf Gordon, 2019/05/07
- Re: Why does close_stdout close stdout and stderr?, Bruno Haible, 2019/05/07
- Re: Why does close_stdout close stdout and stderr?, NeilBrown, 2019/05/07
- Re: Why does close_stdout close stdout and stderr?, Florian Weimer, 2019/05/08
- Re: Why does close_stdout close stdout and stderr?, Paul Eggert, 2019/05/09
- Re: Why does close_stdout close stdout and stderr?, Florian Weimer, 2019/05/09
- Re: Why does close_stdout close stdout and stderr?, NeilBrown, 2019/05/09