Hi,
I have taken a look at this and like Steve, I think the solution is to
find the race condition that causes the problem.
I have committed a change to 2.3.8pre that will check the cause of the
failure to open the file and only open as "w" when its safe to do so (at
least thats the plan).
Hi,
I submitted the bug report plus patch to SourceForge also, because I see
no change here at Debian.
https://sourceforge.net/p/unixodbc/bugs/46/
For almost two years, we have a confirmed problem with libodbc1 *and*
the solution, and the patch is just not going into mainline.
I wonder if
2 matches
Mail list logo
