Thanks, Jim. The traceback I sent earlier. I've attached the contents of the var directory; hope that's what you mean. At 11:48 AM -0500 01/04/1999, Jim Fulton wrote:
Brad Cox wrote:
Could someone please advise on what to do about corrupted data,
We need better tools for diagnosing and correcting this sort of thing. In the mean time, I'd like you to send me (or alternatively support@digicool.com) the corrupted data file and the traceback.
and what might have caused it?
This doesn't happen very often (at all, at least not for us).
It usually happens when multiple processes open the file at the same time, which should generally be prevented by a file lock. It could conceavably happen if a process is killed in the process of writing a record.
I'd like to see the corrupted file to better diagnose the cause and hopefully prevent it in the future.
Also, where is this "/home/brian/temp" stuff coming from? There's no such directory on my system.
This is an artifact of the way that the Python files were compiled. Error traceback show the location where the files were compiled, which is generally different from the run-time locations.
Future binary releases will be made in such a way that relative (to the Zope installation directory) will be stored in the files and shown in tracebacks.
Jim
-- Jim Fulton mailto:jim@digicool.com Technical Director (888) 344-4332 Python Powered! Digital Creations http://www.digicool.com http://www.python.org
Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email address may not be added to any commercial mail list with out my permission. Violation of my privacy with advertising or SPAM will result in a suit for a MINIMUM of $500 damages/incident, $1500 for repeats.
------------------------------------------------ Dr. Brad Cox; 703 361 4751; bcox@virtualschool.edu (update your address book) http://virtualschool.edu/mon A Project with Paradoxical Goals PGP Signature: E194 C6E5 92D8 B8FB 20E8 8667 929A 95A0 FCB6 7C62