Displaying 3 results from an estimated 3 matches for "spawn_work".
Did you mean:
scan_work
2017 Nov 07
2
Problem with getting restapi up&running
...30982] [INFO] Using worker: sync
[2017-11-07 10:29:04 +0000] [30991] [INFO] Booting worker with pid: 30991
[2017-11-07 10:29:04 +0000] [30991] [ERROR] Exception in worker process
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/gunicorn/arbiter.py", line 578,
in spawn_worker
worker.init_process()
File "/usr/lib/python2.7/site-packages/gunicorn/workers/base.py", line
126, in init_process
self.load_wsgi()
File "/usr/lib/python2.7/site-packages/gunicorn/workers/base.py", line
135, in load_wsgi
self.wsgi = self.app.wsgi()
File "...
2006 Aug 24
3
A new QueueWorker class
Hello all,
I''ve come up w/ a worker class that manages queued jobs using a fixed
number of child workers. Well, that''s not quite true -- a new worker is
spawned for each job, but you set the total number that may exist at once.
There are three components:
1) queue_worker.rb: The singleton worker that manages the child workers.
You probably want to auto start this. Make sure you
2006 Aug 08
4
New Release
...t this means is that the autostart stuff now works
correctly because you can always get the same MiddleMan instance from
anywhere within the drb server including your workers. This means
that if you want to, you can start new workers from within a worker
like so:
#in a worker class
@key = spawn_worker :class => :foo, :args => ''whatever''
This also means that you can now finally kill your worker completely
from within itself when you are done with it. THis is for everyone
who needs to fire off a worker and forget it and let it clean up
after itself. To kill a work...