similar to: Mongrel 0.3.13.4 Pre-Release -- PID Files Working

Hi All/Zed, win32 : Is there an Installer/setup for Mongrel along with rails(1.1.6 security patches included) ? Thank you, BR, ~A -----Original Message----- From: Zed Shaw [mailto:zedshaw at zedshaw.com] Sent: Friday, August 11, 2006 11:59 AM To: mongrel-users at rubyforge.org Cc: ruby-talk ML; rails at lists.rubyonrails.org Subject: [Mongrel] [ANN] Mongrel 0.3.13.4 Pre-Release -- PID Files

Hello Everyone, This is a short announce to get people to try the 0.3.13.4 pre-release with their applications. This release features a few things that folks have asked for, and a backport of an enhancement from the 0.4 release coming later. The features are: 1) A new --prefix command line option for people who want to mount their rails app at a different base URI. Thanks to Scott for the

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/

Hello Everyone, I just posted another pre-release of Mongrel that fixes a bug which caused Mongrel to claim it was getting parsing errors because the QUERY_STRINGs were too long. In actuality it was shift in the parser that made empty queries (/test?) become negative. This is fixed up now. Here''s the full list of changes: * It has a couple of fixes for win32, but I still have to

Hi Everyone, Just want to get out another ping on the Mongrel pre-release saga. I''ve updated a bunch of the documentation to include documents people have donated and to beef up the FAQ for most of the questions people have asked over the past month. INSTALL gem install mongrel --source=http://mongrel.rubyforge.org/releases/ CHANGES * Fixed memory leak by switching to Sync rather

Hey Folks, There''s a nasty little bug in 0.3.13.3 when running in development mode which could cause all sorts of problems. Please grab the pre-release of 0.3.13.4 and tell me if it works for you: gem install mongrel --source=http://mongrel.rubyforge.org/releases/ Thanks! -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need

Hi Zed/Jonathan, VMWare Server is free now. http://www.vmware.com/products/server/ http://www.vmware.com/pdf/server_datasheet.pdf www.vmware.com/download/server Runs on any standard x86 hardware * Supports 64-bit guest operating systems, including Windows, Linux, and Solaris * Support for VMware VirtualCenter to efficiently manage infrastructure from a central management console *

Newbie question here: I''m hitting my rails app and killing mongrel. Any ideas? Here''s the error: /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:628:in `accept'': Software caused connection abort (Errno::ECONNABORTED) from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:982:in `join'' from

Apologies, this may be off-topic. I''ve been wrestling with upload issues and Apache 2.2.2 / mod_proxy_balanacer / mongrel_cluster / Mongrel on Mac OS X Server 10.4.5. Typically the first upload would be fine but the next would make the mongrel instance remain running (ps state = "R") essentially locking up that instance. Apache would then eventually do: [Fri Jun 16 16:45:54

Hey Folks, I''ve been rather absent lately, but I now have this week slated for full-time Mongrel development. The goal is to get a few big fixes into 0.3.13.4 and release that, and then get a pre-release of 0.4 out for folks to test against. Please make sure you put any outstanding bugs into: http://rubyforge.org/tracker/?atid=5145&group_id=1306&func=browse And any feature

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

Hey Win32 folks, I messed up the win32 gem for my last Pre-Release announce. Please grab it again with: gem install mongrel --source=http://mongrel.rubyforge.org/releases/ And make sure your apps work with it. Nothing else has changed, but there will be another release for win32 tomorrow. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/

Howdy Folks, This release is after painstaking analysis of a memory leak that was reported by Bradley Taylor, reduced by myself, and then fixed after much work. You should all thank Bradley for finding the bizarre fix. It turns out the Ruby has a memory leak when you use pretty much any thread locking primitive other than Sync (Mutex, Monitor, etc.): http://pastie.caboo.se/10194 The fix (for

Here''s my config: :debug: false :daemon: true - mongrel :log_file: log/mongrel.log :pid_file: log/mongrel.pid :environment: development And I start Mongrel with: mongrel_rails -C config/mongrel.yml It starts up fine, and creates and logs to the log file, but I haven''t seen it create a pid file yet. Any idea why? BTW, why does Mongrel generate a config with vars like :var:

Hi folks, I just put a pre-release of Mongrel up for people to try. You can install it with: gem install mongrel --source=http://mongrel.rubyforge.org/releases/ And try out your application and confirm the stuff works. USE RFUZZ AND RUBY If you find a bug, I''d appreciate it if you can go grab RFuzz (or use net/http) and work up a little bit of Ruby that demonstrates the bug. If

Hi Everyone, I have a small pre-release for Mongrel that will eventually be the 0.3.13.3 release, but it needs some quick testing before I make it official. There''s a bug for only some folks and I need to find out what''s causing it. The bug is that the object_id method gets the signature: def object_id(param) end Which is incredibly evil. Normally this does nothing to

It''s gotta be Rascal. There''s no fixing Victoria - that''s a re-write from the ground up. And Jake a recipe for disaster; Class Jake < Bat include Pig attr_accessor :one_eye . . end That pig ''ll never fly. ---------- Forwarded message ---------- From: mongrel-users-request at rubyforge.org < mongrel-users-request at rubyforge.org> Date:

Hello Everyone, Francois Simond inadvertently found a way to replicate a rare but deadly bug right as I was working up the official release of Mongrel 0.3.13. This bug only happened to a few people, but thanks to the wonderful fuzzing tool Apache Bench[1] he could replicate the slow select starvation people were seeing. TESTING This bug is now fixed in the current pre-release, and I''d

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

Hey Folks, I''ve been meeting lots of great folks at RailsConf and in my spare time hacking up this latest pre-release of Mongrel. It features the following new goodies: * Change to user:group is done *after* the socket is bound, but still as early as possible. * Mongrel will try to reap dead threads as soon as possible, especially when it gets overloaded with too many open files. *