It's not segfaulting. Running the start script with "-Z ''", it gives me: Traceback (most recent call last): File "/export/home/local/Zope-2.4.3-solaris-2.6-sparc/z2.py", line 774, in ? asyncore.loop() File "/usr/local/stow/Python-2.1.1/lib/python2.1/asyncore.py", line 194, in l\ oop poll_fun (timeout, map) File "/usr/local/stow/Python-2.1.1/lib/python2.1/asyncore.py", line 86, in po\ ll r,w,e = select.select (r,w,e, timeout) select.error: (4, 'Interrupted system call') I can trigger this by closing and attempting to reopen my Oracle connection. On Wednesday, December 12, 2001, at 05:17 PM, Richard Jones wrote:
On Thursday 13 December 2001 8:23 am, Jin Choi wrote:
I was able to get consistent Zope failures on Solaris w/ DCOracle2 by disconnecting and reconnecting the connection in the Product management interface. If I run the server without the zdaemon, it prints that there was an interrupted system call on a "select()".
Dario, this is Zope 2.4.3 running with Python 2.1.1 on a Solaris 2.8 server, with Oracle 8.1.7 and the latest recently released DCOracle2 driver.
This is the first I've heard about Python 2.1 and Solaris not getting along. Is 2.2 any better?
There is this which is fixed in both 2.2 and 2.1.2:
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=471942&group_id= 5470
Is that the behaviour you're experiencing?
Richard