fix resque start task

apply changes from Resque::Queue.new changes
move worker settings out of begin block, since they shouldn't raise
ArgumentError

Author: Aaron Patterson and Terence Lee

lib/resque/tasks.rb

@@ -11,14 +11,15 @@
     queues = (ENV['QUEUES'] || ENV['QUEUE']).to_s.split(',')
 
     begin
-      worker = Resque::Worker.new(*queues)
-      worker.verbose = ENV['LOGGING'] || ENV['VERBOSE']
-      worker.very_verbose = ENV['VVERBOSE']
-      worker.term_timeout = ENV['RESQUE_TERM_TIMEOUT'] || 4.0
-    rescue Resque::NoQueueError
+      worker = Resque::Worker.new(queues)
+    rescue ArgumentError
       abort "set QUEUE env var, e.g. $ QUEUE=critical,high rake resque:work"
     end
 
+    worker.verbose = ENV['LOGGING'] || ENV['VERBOSE']
+    worker.very_verbose = ENV['VVERBOSE']
+    worker.term_timeout = ENV['RESQUE_TERM_TIMEOUT'] || 4.0
+
     if ENV['BACKGROUND']
       unless Process.respond_to?('daemon')
           abort "env var BACKGROUND is set, which requires ruby >= 1.9"