Skip to content
This repository

Incorrect code example removed #60

wants to merge 1 commit into from

1 participant

Pankaj Tyagi
Pankaj Tyagi

See comment on issue #43.

This actually does not work. The first worker will block the next until it receives a kill (TERM or INT) and then the next one starts. This is not multiple works but running three one after the other. Please remove this incorrect documentation as it will cause people to waste time trying it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Showing 1 unique commit by 1 author.

Mar 07, 2013
Pankaj Tyagi ptyagi16 Incorrect code example removed 5a3d451
This page is out of date. Refresh to see the latest.

Showing 1 changed file with 1 addition and 9 deletions. Show diff stats Hide diff stats

  1. +1 9 README.textile
10 README.textile
Source Rendered
@@ -99,15 +99,7 @@ You can also run by writing a simple @script/job_runner@, and invoking it extern
99 99 </code></pre>
100 100
101 101 Workers can be running on any computer, as long as they have access to the database and their clock is in sync. You can even
102   -run multiple workers on per computer, but you must give each one a unique name:
103   -
104   -<pre><code>
105   - 3.times do |n|
106   - worker =
107   - = 'worker-' + n.to_s
108   - worker.start
109   - end
110   -</code></pre>
  102 +run multiple workers on per computer, but you must give each one a unique name.
111 103
112 104 Keep in mind that each worker will check the database at least every 5 seconds.
113 105

Tip: You can add notes to lines in a file. Hover to the left of a line to make a note

Something went wrong with that request. Please try again.