[ZODB-Dev] zeo 2: asyncore?

[Chris McDonough]

Mark,

How about a "voodoo" shot in the dark. ;-)

Right after the lines in z2.py that read:

# Jigger path:
sys.path=[os.path.join(here,'lib','python'),here
          ]+filter(None, sys.path)


Put this (embarrassing) piece of code:

seen = {}
l = []
for name in sys.path:
   if not seen.has_key(name):
       l.append(name)
   seen[name] = 1

sys.path = l

I had a similar problem lately that I never did figure out properly, but
it had to do some similar path munging before things righted themselves.

- C

On Wed, 2002-09-04 at 16:42, Mark McEahern wrote:
> I've been trying unsuccessfully to get ZEO2 (2.0b1) to work with Zope 2.5.1
> on Red Hat 7.3.  Both Zope and ZEO seem to start just fine.  I look in the
> STUPID_LOG_FILEs (I have one for each) and nothing's obviously screwy.
> However, when I go to access Zope in the browser, it times out.  I came
> across a reference in the ZEO source (ZEO/misc/custom_zodb.py) to an
> asyncore discrepancy.  If I look in:
> 
>   $ZOPE/ZServer/medusa/asyncore.py
> 
> I see this comment:
> 
>   # NOTE: this is a difference from the Python 2.2 library
>   # version of asyncore.py.  This prevents a hanging condition
>   # on Linux 2.2 based systems.
> 
> Could this somehow be causing my problem?
> 
> // mark
> 
> -
> 
> 
> _______________________________________________
> For more information about ZODB, see the ZODB Wiki:
> http://www.zope.org/Wikis/ZODB/
> 
> ZODB-Dev mailing list  -  ZODB-Dev@zope.org
> http://lists.zope.org/mailman/listinfo/zodb-dev