Re: Bug: tests/fsync.c: don't check for fsync failure on invalid fd

[Phillip Susi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 3/13/2013 11:30 AM, Paul Eggert wrote:
> Gnulib is an application that easily found out that the library
> violates POSIX, which indicates that the library's main point is
> not properly supported.  There should be an easy fix, no?

Gnulib isn't an application; it's a library that provides portability
workarounds for applications.  It is attesting to the applications
built with it that they can rely on fsync returning EBADF when given a
bad file descriptor.  The question I keep asking and not getting an
answer to is why it bothers doing this?  Is there an application that
actually depends on this being true, or is it a totally useless test?
 If it is a useless test, then the test should be removed rather than
burden every other task with making a syscall they don't need.



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRQKGfAAoJEJrBOlT6nu759BMH/3MEcOT6K8WBcEBJd297uEmK
lviRuSV4HejCJ2JrS+Mm41WH+GBuvSyg1KY4lnt8X85SGScPiZ5pNzEMkBBN/snt
WF4YfvCwORfddEuyO0X7yW7TWKyrlpRXM5aTaynsGbMDt8xAo0xon61e8EaMWPMf
o3rRZddw2Q13znr0BSB/cpAaD5gvgoH7DuxljzxiaNttvUPyFavU3mF1U5HJjA11
j/AVkHppgEwDOT5vfFFv8T73sGYlLw2COZthlYP22Z72SH8zG1HWZHaCas9aqDEa
RXTWUOFdHf+LQJswhZuowI5i3sypGNy/LuWzW/4EgKQZjFWPjoDCmgs2APJW/0g=
=hw+E
-----END PGP SIGNATURE-----