RE: directory storage is not responding
Stefano Maffulli <[email protected]>
| Newsgroups | gmane.comp.web.zope.zodb.dirstorage |
|---|---|
| Message-ID | <1089389509.2705.122.camel@plusultra> |
On Fri, 2004-07-09 at 17:28, Toby Dickenson wrote: > > I tried removing (--purge zope*) and reinstall from debian unstable > > (zope 2.6.4): default instance with Data.fs works. I duplicate the > > instance, install dirstorage (1.1.9 this time), create a dirstorage > > from the previously working Data.fs, start the instance: it hangs > > and looks at invisible butterflies, again. > > You have a small Data.fs that works, and it makes zope hang when > converted to a DirectoryStorage? exactly. > If you can email me a copy of the Data.fs and tarball of the storage > to [email protected], I will see if I can reproduce. I am not sure that it is the fault of the data, but I will try to send you the tarball. > Have you any clue about where it is hanging? According to strace, it hangs after the first fork(). I can send you the strace output if you want. > Im not aware of any code to do that, but it wouldnt be hard. The > Full.py history method has all the logic needed for traversing the > storage, and FileStorage has a 'restore' method which can be used to > insert the data. The only tricky part is that DirectoryStorage history > is linked starting with recent history but FileStorage.restore wants > old history first, so you need to reverse the transaction order. I'll keep this info here for now, I hoped there was something already done :) regards stef ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com