Hi Ron. I found the following trying to follow up a bit on what you
have suggested. I believe it is similar to what you are doing from your
explanation. It may be out of date. I have not attempted to
daemonize a process to date so it would be great if you could look at
this and comment since I need something to work with.
As far as interacting with Zope, I have done something similar to build
a site remotely from another server but setup https and sent
credentials in the urls. I wonder if there is a way to inject them
into Zope another way since the daemon is on the machine. I think the
ClockServer injects requests into Zope. I believe it is something
similar since credentials still need to be in url to execute something
but requests are not exposed to the web doing this.
On Wednesday, September 14, 2005, at 12:11 AM, Ron Bickers wrote:
On Tue September 13 2005 08:16 pm, David Pratt wrote:
How is it that you send a signal to the long running
The long-running process writes a pid file and waits for a SIGUSR1
(using Python's signal module). A small External Method, called when
user submits the form, reads the pid file and sends the signal to the
Is the long running process cronned to look for a record in
the database or is this starting another server of some type.
It waits for a SIGUSR1 signal from the website, otherwise it's idle.
way it can begin processing immediately but doesn't have to do any
checking. I do, however, have a cron job that starts it every 15
case it dies. The process knows if it's already running, so it's safe
just start it regularly.
What I need is something like what you are suggesting - wakes up when
there is work in the hopper and chugs along until it is done and then
goes to sleep (sort of the way a printing queue works). At the same
time it would be great if it was something that had a small RAM
footprint or ran without consuming any more than X mbs.
The part that waits for the signal is very small, but it loads the
modules and reads a bunch of data to do the work, so it can get large
times. If it were to just call an external program that dies after
its work, you could easily keep memory usage low.
problem I have with this is that it needs to do work in Zope itself
since the final docs end up as objects. I have just found Chris
Wither's product called Stepper. I am not sure it this is for this
of situation or more for cronned maintenance.
I have no idea. Maybe it'll do what you want, but I don't understand
really does just from the description. The work I needed to do was
to Zope anyway (reading data from a MySQL database, building PDFs with
Reportlab, sending email), so it's actually better that I'm outside of
When I have to run things in Zope from outside, I run curl with a URL
Python Script that does the work. It's a hack, but I've never had a
with it. I'm not sure how else you would work in Zope from a process
outside of Zope.
Zope maillist - Zope@zope.org
** No cross posts or HTML encoding! **
(Related lists -