1. How to automatically delete worker when the job is done?
2. Must the backgroundrb be restarted if the worker code has changed. Or
is there another way.
If it has anything to do with this I have :rails_env: development
Posted via http://www.ruby-forum.com/.
Re: Backgroundb question
On 7/18/07, Damjan Rems <email@example.com> wrote:
> Two actualy:
> 1. How to automatically delete worker when the job is done?
> 2. Must the backgroundrb be restarted if the worker code has changed. Or
> is there another way.
> If it has anything to do with this I have :rails_env: development
for deleting a worker, when its done, you can call self.delete from
worker or worker.delete from outside, where worker is an instance of
your worker. You can also call exit from the end of worker to stop its
existence(this works because, each of your worker is a process of its
Yes, you need to restart your worker, if you have changed code and it
has nothing to do with rails environment you are in.
Let them talk of their oriental summer climes of everlasting
conservatories; give me the privilege of making my own summer with my
|Thread||Thread Starter||Forum||Replies||Last Post|
|Re: question about data values||Frank Schiffel||Newsgroup comp.soft-sys.sas||0||06-28-2005 12:01 AM|
|Re: question about data values||toby dunn||Newsgroup comp.soft-sys.sas||0||06-27-2005 11:40 PM|
|Re: Question about Input Control Data Set / PROC FORMAT||Michael S. Zdeb||Newsgroup comp.soft-sys.sas||0||06-27-2005 04:16 PM|
|Re: Question on Proc SQL - correct age formula||Sridhar, Kumar||Newsgroup comp.soft-sys.sas||0||05-24-2005 05:23 PM|
|Re: OT Bit Buckets (was RE: Mainframe and caps (was: A question about macro quote))||Dunn, Toby||Newsgroup comp.soft-sys.sas||0||11-24-2004 01:25 PM|