Re: Re: [Zope-dev] ERROR(200) ZODB Couldn't load state for... Memory problem?

2004-07-23 Thread Chris McDonough
On Fri, 2004-07-23 at 16:21, Tim Peters wrote: > [Chris McDonough] > > ... > > self._f[current] = open(self._p[current],'w+b') > > > > will be likely to fail at the last line if you're using > > nonpersistent cache files, because self._p[current] is (bogus) > > '1-None-0' (relative b

Re: Re: [Zope-dev] ERROR(200) ZODB Couldn't load state for... Memory problem?

2004-07-23 Thread Tim Peters
[Chris McDonough] > ... > self._f[current] = open(self._p[current],'w+b') > > will be likely to fail at the last line if you're using > nonpersistent cache files, because self._p[current] is (bogus) > '1-None-0' (relative bogus filename). Is it really *likely* to fail? It's just a

Re: Re: [Zope-dev] ERROR(200) ZODB Couldn't load state for... Memory problem?

2004-07-22 Thread Tim Peters
[Chris McDonough] > ... > I think the problem is related to ZEO client storage "cache flips". Me too. The 3.2 ZEO cache alternates between two cache files, in the two-element list self._f. Both elements are initialized to None, and the index of the current file in use (0 or 1) is in self._curren