I suspect some sort of race condition between two mysql_safe processes. At least, every time I experienced this bug, there were at last two mysql_safe processes active, and at least one of them was running amok.
I suspect some sort of race condition between two mysql_safe processes. At least, every time I experienced this bug, there were at last two mysql_safe processes active, and at least one of them was running amok.