Re: Spurious "file has changed on disk" warnings on Linux
Charles G Waldman writes:
On a more general note, why is HAVE_FSYNC being handled the way it
is
(in src/sysfile.h) instead of by the configure script? The existing
logic seems convoluted - since Linux #defines USG, sysfile decides not
to #define HAVE_FSYNC, even though Linux has fsync. Am I
misunderstanding the purpose/meaning of the HAVE_FSYNC symbol? What
does USG have to do with it?
The USG conditionals hearken back to simpler times. USG
vs. BSD used to be 80-100% of what you had to know to port
UNIX applications. Things have gotten progressively worse
since then.