title: bluepill not detecting that processes have, in fact, started successfully, and so creates new ones
body: <p>I have one (EC2) Ubuntu server where <code>bluepill</code> is working just fine to start and monitoring <code>resque</code> processes (and it has done so on other nodes in the past).</p>
  
  <p>I'm setting up a new node, and for some reason on this node <code>bluepill</code> does not recognize that the processes have started and are running, and so keeps creating new ones.  I'm a little baffled by what's causing this.  The 2 nodes are almost identical; they're both EC2 servers provisioned by the same <code>chef</code> scripts.  It is true that the one not working is 'production' and the other 'staging', but there's almost no difference due to that.</p>
  
  <p>Any thoughts or suggestions before I fork the github project and start inserting more monitoring, to try and figure out what's going on?  There's been discussion on this list in the past about troubles w/ <code>bluepill</code> and <code>resque</code>, but as I said this is working fine on my staging server, and has worked fine on earlier production servers (although I will note that this new production server is ruby 1.9.3 (vs 1.9.2) and rails 3.2 (vs. 3.1)).</p>
  
  <p>Here's my <code>.pill</code> file (or more specifically, my <code>chef</code> cookbook's template file):</p>
  
  <pre><code>ENV["RAILS_ENV"] = "&lt;%= node.chef_environment %&gt;"
  ENV["QUEUE"] = "*"
  
  Bluepill.application("zmx_app") do |app|
    app.working_dir = "/srv/zmx/current"
    app.uid = "root"
    app.gid = "root"
    2.times do |i|
      app.process("resque-#{i}") do |process|
        process.group = "resque"
        process.start_command = "rake resque:work"
        process.pid_file = "/srv/zmx/current/tmp/pids/resque_workers-#{i}.pid"
        process.stop_command = "kill -QUIT {{PID}}"
        process.daemonize = true
      end
    end
  end
  </code></pre>