On Mon, Dec 01, 2008 at 03:42:05PM -0500, Dan Barker wrote: > How do I go about trapping this error in locker? (Specifically, how do I > figure out who Called locker, to find the code that's not closing the file > it opened?) > > Has anyone else run into this sort of issue?
The last time this sort of issue came up, it was traced back to a bug in DB_File. Specifically, the untie call would actually not let go of the DB. SA doesn't actually open the database files itself, it lets tie/untie (DB_File) deal with it. -- Randomly Selected Tagline: "It is our job to protect the magic smoke ..." - Prof. Michaelson
pgpazod0q97W7.pgp
Description: PGP signature
