]> git.ipfire.org Git - thirdparty/sqlite.git/commit
Closing a file from the wrong thread is harmless on most systems.
authordrh <drh@noemail.net>
Sun, 15 Jan 2006 02:43:16 +0000 (02:43 +0000)
committerdrh <drh@noemail.net>
Sun, 15 Jan 2006 02:43:16 +0000 (02:43 +0000)
commit3832230e25e6ee8368417d0a241e9546c60d9535
tree9cd61db3bab5141b75b5395d8c7bdb03f49062d1
parent64b1bea3ba506ebd4d2730f9a7450289a9e9b4fc
Closing a file from the wrong thread is harmless on most systems.
(See ticket #1611)
But on systems like RedHat9 with broken fcntl() locks, it leaks file
descriptors.  That is better than the alternative of prematurely breaking
locks and causing database corruption.  Nevertheless, it would be good
if we could figure out a way to report errors when closing a file from
the wrong thread. (CVS 2946)

FossilOrigin-Name: ad8f12cad1fcd9c54478abe20050f9a953035506
manifest
manifest.uuid
src/os_unix.c