[Tim Golden]
>> Wasn't sure about that; thanks for clarifying. I'm
a little
>> confused; am I the first person to experience this?
Is there
>> something unusual in my setup that doesn't occur
elsewhere?
>> (Win32 perhaps?). I'm happy to provide a doc patch,
but best
>> not if it's some localised condition no-one else
will meet.
[Robert Brewer]
> You're not the first; a doc patch would be most
welcome.
Happy to oblige. The only thing is: I'm not sure what
I'm patching - the docstring? one of the several wiki
pages? And the only *other* thing (!) is that I'm not
sure what I'm documenting. See: tons of goodwill; not
many clues.
In short, I can happily provide text which says:
"""
Possible problem using mod_python:
If you encounter "Unrecoverable error in the
server"
or, with logging turned on, an error which seems
related to threads and signals, then try adding
the following lines to your cherrypy module before
the engine is initialised:
cherrypy.engine.SIGHUP = None
cherrypy.engine.SIGTERM = None
"""
(in fact - there it is) and this would at least save
someone in the future from having to sweat a few hours
of trial-and-error. But is there some deeper malaise?
Should the CP engine be *trying* to send signals when
not in the main thread? What's the impact of turning
the signals off?
[Robert B]
> I found your AD work and misc win32 howtos quite
beneficial, too.
> Thanks!
Glad to be of service I'm
certainly glad that
cherrypy's around - isn't the Python community great?!
TJG
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "cherrypy-users" group.
To post to this group, send email to cherrypy-users googlegroups.com
To unsubscribe from this group, send email to
cherrypy-users-unsubscribe googlegroups.com
For more options, visit this group at h
ttp://groups.google.com/group/cherrypy-users?hl=en
-~----------~----~----~----~------~----~------~--~---
|