Ticket #14 (closed bug: fixed)

Opened 7 months ago

Last modified 1 month ago

mongrel_rails command line option --num-procs does not change the max number of procs

Reported by: evanweaver Assigned to: evanweaver
Priority: minor Milestone: 1.2
Component: Mongrel Keywords:
Cc:

Description

The --num-procs parameter does not seem to work. To debug the problem I added STDERR.puts "TEST: #{worker_list.length} #{@num_processors}" on line 279 of /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.3/lib/mongrel.rb, and to my surprise it looks like the parameter is ignored. If I run it $ mongrel_rails start -a 127.0.0.1 -p 8999 --num-procs 1 & [1] 18617 ** Starting Mongrel listening at 127.0.0.1:8999 ** Starting Rails with development environment... config/boot.rb:28:Warning: require_gem is obsolete. Use gem instead. ** Rails loaded. ** Loading any Rails specific GemPlugins? ** Signals ready. TERM => stop. USR2 => restart. INT => stop (no restart). ** Rails signals registered. HUP => reload (without restart). It might not work well. ** Mongrel 1.1.3 available at 127.0.0.1:8999 ** Use CTRL-C to stop.

and then:

$ w3m -dump http://localhost:8999/test >/dev/null TEST: 0 950 $

So it looks like @num_processors is still at the default value of 950, and not 1 as I told it on the command line.

Attachments

0001-mongrel_rails-support-n-num-procs-command-line-o.patch (2.5 kB) - added by normalperson on 02/25/08 01:03:38.
mongrel_rails: support -n/--num-procs command-line option

Change History

02/25/08 01:03:38 changed by normalperson

  • attachment 0001-mongrel_rails-support-n-num-procs-command-line-o.patch added.

mongrel_rails: support -n/--num-procs command-line option

02/29/08 17:33:25 changed by evanweaver

  • milestone changed from 1.3 to 1.2.

03/23/08 22:49:40 changed by evanweaver

  • status changed from new to closed.
  • resolution set to fixed.

08/10/08 02:59:48 changed by airforce1

I'm closing it according to the last comment.
----------
dancing air jordan