On a side note, I looked into gdbmclose.c, and it does *no* error checking on the fsync() or close() calls, which means (from this simple look, at least) that it's not guaranteed that the data is safe (eg. with disk full).
Maybe that alone would warrant removing that fsync(), but checking the return code of close(). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
