Hi Tim,
Tim Peters wrote at 2004-6-27 17:06 -0400:
[Dieter Maurer]
The problem occured in a ZEO client which called asyncore.poll
in the forked subprocess. This poll deterministically
stole ZEO server invalidation messages from the parent.
I'm sorry, but this is still too vague to guess what
[sathya]
so can we safely assume that zeo does not mix the asyncore implementation
with forks or threads and hence does not suffer from the child
concurrently operating on sockets along with parent syndrome that
dieter is experiencing ? appreciate any clarifications.
It's normal for a ZEO
Tim Peters wrote at 2004-6-27 04:46 -0400:
...
[Dieter]
When a process forks the complete state, including file descriptors,
threads and memory state is copied and the new process
executes in this copied state.
We now have 2 asyncore threads waiting for the same events.
A problem is
[Dieter Maurer]
The problem occured in a ZEO client which called asyncore.poll
in the forked subprocess. This poll deterministically
stole ZEO server invalidation messages from the parent.
I'm sorry, but this is still too vague to guess what happened.
- Which operating system was in use?
-
Tim Peters wrote:
hello tim,
so can we safely assume that zeo does not mix the asyncore
implementation with forks or threads and hence does not suffer from the
child concurrently operating on sockets along with parent syndrome
that dieter is experiencing ?
appreciate any clarifications.
