>> So unless we've got a bona fide HP/UX expert on tap now (do we? that >> would be way cool <wink>), don't hold up solving a clear and >> widespread Linux problem by waiting for one to appear.
Jason> Just to be clear, the os.fsync() problem is not Linux-only. It's Jason> also on FreeBSD (probably every Unix platform actually).
Correct. There are two new C macros in pyconfig.h, HAVE_FSYNC and HAVE_FDATASYNC. When originally added, the former was mistyped as HAVE_SYNC.