Posted so anyone else Googling "sqlite hang" can find this.
We sometimes get persistent Sqlite database busy errors with
no apparent cause (all processes killed, etc) and no help from
the do***entation. I found one cause:
We open the sqlite database, some/path, with different uids.
Blown transactions can leave a some/path-journal file which
is mode 600 to the opener uid only; other uids cannot read the
journal and clear out the deceased transaction.
I dewedged sqlite by deleting the journal file. I didn't think
of trying chmod a+rw until later, so I don't know if that will
also work with less risk of damage.
--
SM Ryan http://www.rawbw.com/~wyrmwif/
Leave it to the Catholics to destroy existence.
