Let's see: network lookups would fail, sometimes, strangely, signals would be delivered to _all_ children (not just the one that had installed a signal handler) -- so if you had an external method that popen'd another program, when the SIGCHLD came in, it would kill the mainloop. The signals were the really shocking problem. Anthony.

...

...

Tony McDonald wrote At 5:48 pm +1000 19/5/00, Anthony Baxter wrote: If you're running a Zope on Solaris2.7 and you're seeing strange behaviour, make sure that your python executable's been built and linked with pthreads, not solaris threads. I've just had a horrible time figuring out why I was seeing very strange behaviour on Solaris until I noticed this.

ldd `which python` should show /usr/lib/libpthread.so, NOT /usr/lib/libthread.so.

Can you tell us what kind of behaviour Anthony?

I'm using 2.6 on our main box (and 2.7 on another dev. box).

cheers, tone ------ Dr Tony McDonald, FMCC, Networked Learning Environments Project http://nle.ncl.ac.uk/ The Medical School, Newcastle University Tel: +44 191 222 5888 Fingerprint: 3450 876D FA41 B926 D3DD F8C3 F2D0 C3B9 8B38 18A2

_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )

-- Anthony Baxter <anthony@interlink.com.au> It's never too late to have a happy childhood.