Re: Spurious "file has changed on disk" warnings on Linux
Charles G Waldman <cgw(a)pgt.com> 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?
Only Martin is truly competent to answer this, but if I had to guess,
I'd say it's a remnant of the pre-configure period, when all the
HAVE_* symbols were handles by s/m files. If we want to use
HAVE_FSYNC, we should simply check it via Autoconf.
--
Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Predestination was doomed from the start.