similar to: mongrel_rails: bug in -C handling?

Alright, this time a small announce going out to *just* the mongrel list so I can get some early testing. There''s a new pre-release of 0.3.13.4 out that includes the win32 version of the gem. ** WIN32 USERS SHOULD INSTALL THIS AND TEST.*** ***** BUT NOT ON PRODUCTION SYSTEMS. ****** As usual, you install it with: sudo gem install mongrel --source=http://mongrel.rubyforge.org/releases/

I''m trying to run mongrel on port 80 and switch to a different user/group from root. As root, this works: mongrel_rails start -p 3000 -u rails --group rails This: mongrel_rails start -p 80 -u rails --group rails dies with: --------------------------- ** Changing group to rails. ** Changing user to rails. ** Starting Mongrel listening at 0.0.0.0:80

Hi, why are the gemplugins commented out in mongrel_service? What was the problem with them? I''m curiuos because I''ve used them without problems since the revision 338 (-win32 suffix patch, 31/08). However, my site is a small internal one, so it doesn''t mean any heavy testing. Jano

Hello Folks, This is the long awaited release of the Mongrel HTTP library that supports *Ruby On Rails*. I know tons of people have been waiting for it, so I''ve got a few things to lay down first before you get all excited: 1) It''s very very ALPHA support for Rails. It will run a Rails app, and runs my simple apps, but it''s not fast or correct as it needs to

Hello, I have mongrel 1.0.1, rails 1.2.2 ruby 1.8.5 running on Centos 4.4. When I execute the mongrel_rails start -d I see that 3 processes are spawned. See below: [root at ccc aaa]# mongrel_rails start -d [root at ccc aaa]# ps -def |grep mong root 2743 1 9 07:14 ? 00:00:01 /usr/bin/ruby /usr/bin/mongrel_rails start -d root 2744 2743 0 07:14 ? 00:00:00

Ok, I have checked in the first draft of rails win32 service into examples mongrel_rails_service is the controller, and the _svc script is actually the service. The controller uses Mongrel Commands as requested by Zed, but the service was simplified for debugging purposes, later will merge and refactor both files. The environment defaults to production, so if wanted to run it on other, you must

Hi, On os x.3.9, with ruby 1.8.4 installed through darwinports and mongrel through gems, everything works until I restart: mongrel_rails restart adds the logs: ** USR2 signal received. ** Restarting with arguments: ruby /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/bin/mongrel_rails start -p 3001 -d /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/bin/mongrel_rails:134: in

Hi folks, I''ve been working on the plugins system this weekend and I think I''ve nailed it down. The system will basically be able to load gems that are configured right to be plugins. It''ll do it fairly dynamically and shouldn''t require any configuration from the end user other than to install the gem. Doing this though will involve a bit of surgery on the

Hello All, Yet another release of Mongrel proudly pushed out for everyone to review and comment on. This time though, I''ve done up a little website that''s *way* better than the plan Rdoc that used to stand in for the site like a one-legged leper. * http://mongrel.rubyforge.net/ As you should already know, Mongrel is a fast HTTP server and library for Ruby partially written in

I tried using the killall -USR1 mongrel_rails to check on a problem, and all I get is mongrel_rails: no process killed Nothing shows in the log. Any ideas? I''m using the latest pre-release, and a ''ps'' shows my cluster is running. Cheers, Brett

mongrel_rails cluster::start doesn''t seem to pay attention to whether or not the processes exist or not. If you run it twice, the first set of processes are created, then then second run will overwrite the log/{pidfiles} files with the new process numbers. Problem is that the second group of processes are gone, since the first ones had the port open. I''d think that the right

Hello Everyone, This is the official 0.3.13.3 release of Mongrel. Mongrel is now released under the *Ruby license* instead of the LGPL. I''m hoping this increases the adoption of Mongrel even further and hopefully I can start pushing to get Mongrel included in Ruby directly. INSTALL As usual, you install it with your friendly gem install method of choice: gem install mongrel Or

Just a quick note for a few new features/fixes available on the Mongrel pre-release and a new document that covers nearly all the big features and configurations for Mongrel. First, the document is http://mongrel.rubyforge.org/docs/howto.html and it covers: * All the start command options including the fresh -G option to generate a config for -C. * The format and usage of the MIME type file (-m

Following is the output of top command at my server and i find the high usage very much alarming. We are basically a team of three developers working on same machine(remotely), so we run mongrel_rails servers from out ~/public/app directories. We also run a cluster of mongrel servers using apache2.2. Is this much memory use normal? PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+

Hey Folks, I''ve been holding off the official 0.3.13 release so that Luis can get the win32 side very nice and clean. We fixed a major problem last night so it''s only a short time before we get it out. Luis is working really hard on it, so just be patient. In the meantime, I''ve been doing a code audit of the Mongrel code as it is now and fixing any little things I

I''m having no luck trying to daemonize mongrel running a camping server. When mongrel daemonizes, I get: /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:723:in `accept'': closed stream (IOError) from /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in `join'' ... (This was after I disabled the unhandled exception catchall in the

Hello Everyone, Today''s Mongrel is the first release to sport spiffy pre-built win32 gems. This comes thanks to Wilson Bilkovich donating some Rakefile magic that does the stuff for me. Everyone who uses win32 should send Wilson a thank-you since without him you''d be a victim of my laziness for at least a few more weeks. People who are testing and trying Mongrel out should

I do some indexing using acts_as_ferret in a rails app. I need to do some preloading of the index''s sort fields so that the first request that sorts doesn''t take 5 minutes to complete. I tried sticking my preload code in config/environment.rb and that worked but it gets ran in rake migrations, tests, etc, when it''s not really needed. Is there anything specific to

Following errors are taken from monrgrel running in development mode. It complained routes.rb, no such file or directory and then sometimes i get application.rb, no such file or directory.Doesn''t seem correct to me. Though not so often, but even production servers throw these errors sometimes, and i have no special routes setup or something.Its pretty much default one, except few changes

Hello Windows Users! I have finally got my new computer with it''s win32 build working and have just done the first pre-release for 0.3.13 that has win32 support. *** All win32 users should try to grab the pre-release and tell me if it works. *** You can install it with: $ gem install mongrel --source=http://mongrel.rubyforge.org/releases/ >From EITHER win32 or any other platform