similar to: Thanks For The Present!

On 1/23/07, mongrel-users-request at rubyforge.org < mongrel-users-request at rubyforge.org> wrote: > > > Date: Mon, 22 Jan 2007 21:48:21 -0800 > From: "Zed A. Shaw" <zedshaw at zedshaw.com> > Subject: [Mongrel] [ANN] Mongrel 1.0.1 Officially Released > To: mongrel-users at rubyforge.org > Message-ID: <20070122214821.4804e941.zedshaw at zedshaw.com>

Calling All Mongrel Minions! I wanna have some fun and would like this as a Christmas present. The site http://www.workingwithrails.com/ has this lame popularity system that''s kind of irking some of the main Ruby contributors. I think it''s kind of funny, but would like to demonstrate what an army of motivated people can do to these kinds of popularity contests. So, as a

I really wanted to thank everyone personally for voting for me, but man I don''t have the time. So, like a good programmer I just automated it with espeak: $ speak -w thank_you_everyone.wav -s 168 -v en/en-f -p 60 -a 120 -l 50 -f who.txt $ lame -V2 thank_you_everyone.wav thank_you_everyone.mp3 And now you all get a personalized thanks from some electronic British woman:

Alright folks, I put in a fix for camping and added the patch by Thomas Hurst for the accf_http deferred accept settings for FreeBSD. As usual, please test this release out and let me know if it has any additional problems. I''ll be working on win32 builds today and tomorrow with Luis. Install with: sudo gem install fastthread --source=http://mongrel.rubyforge.org/releases sudo gem

Hi Everyone, There''s quite a few of you who have contacted me about Mongrel suddenly stopping. After a lot of investigation, I found that the common thread between all of you is memcache and Eric Hodel''s memcache-client. People who were running this combination would have intermittent pauses and investigating the stalled mongrels showed that memcache-client was waiting for

It''s time again for your monthly cgi.rb DOS vulnerability. This latest vulnerability is different from the one that cgi_multipart_eof_fix.gem fixed. This one is related to the boundary taken from the web client being used incorrectly. You can read about the vulnerability: http://www.ruby-lang.org/en/news/2006/12/04/another-dos-vulnerability-in-cgi-library The applicable PATCH is

I received this piece of code in a patch that turns on the FreeBSD http filtering. I completely missed that it calls /sbin/sysctl directly which means I''m slipping on my auditing. def configure_socket_options case RUBY_PLATFORM when /linux/ # 9 is currently TCP_DEFER_ACCEPT $tcp_defer_accept_opts = [Socket::SOL_TCP, 9, 1] $tcp_cork_opts =

Another fancy release with just a few little changes from yesterday: * Set-Cookie, Set-Cookie2, Warning, and WWW-Authenticate are allowed as duplicate headers. * mongrel_rails stop now has a --wait option to go with --force. It will wait for either the given timeout in SECONDS or the PID file to go away. If the PID file goes away it just exits. If the timeout happens then it does a kill -9 on

Hi folks, I took a break from Mongrel today and instead whipped up an Atom feed generator for my site. People who love or utterly hate my essays will lover or utterly hate to subscribe to it. http://www.zedshaw.com/feed.atom Let me know if it isn''t working well in your favorite feed reader. -- Zed A. Shaw, MUDCRAP-CE Master Black Belt Sifu http://www.zedshaw.com/

Hello Everyone, We''re hard at work getting the hot new win32 service Luis wrote out and ready for production. We''re hoping to have that included in the 1.0 RC1 release we make very soon. This pre-release is just to make sure that we didn''t step on any toes. Install it with: $ gem install fastthread --source=http://mongrel.rubyforge.org/releases $ gem install

Hey Everyone, Topfunky (Geoffry) has created a great PeepCode screencast on using httperf to performance measure your web applications: http://nubyonrails.topfunky.com/articles/2007/03/05/peepcode-page-caching-and-httperf http://peepcode.com/products/benchmarking-with-httperf Topfunky put a ton of work into this and really got it right. The attention to detail is very good and he researched

Hello All, I''m putting out a quick half-release because there''s some work on the MIME types I''ve included that needs to be done by all of you. Read at the end to understand your role in what you started. This release features two major capitulations on Mongrel''s stance of not being a full web server. The first is Mongrel now sports a YAML file with 739 MIME

There seems to be a bunch of books now that either mention Mongrel or focus on it or will focus on it. I''ve got my book, but the more books that people can easily get in as many languages as possible benefits Mongrel and everyone. Soooo, I''m gonna start a "Books" page that will list all the books that talk about Mongrel. Send me your book, a small abstract, and the

Hi folks, Getting much much much closer to the 1.0 release. I have some documentation to work on tonight, and I need to go through the patch queue one more time, but I''ve put up another pre-release for people to test. What this pre-release does is pull together the various patches, monkey patching, and alternatives that make Mongrel either faster or more stable. It is also the start

Hi, Thanks Zed - this is very interesting. One item in particular caught my eye: Does anyone on this list have any comments or validation that Rails 1.2.1 is 2-4 times as slow as Rails 1.1.6? Topfunky provided a link that purports what looks like really horrible performance and memory characteristics for Rails 1.2.1, even v. 1.1.6:

Someone contacted me earlier today and pointed out this typo in the mongrel apache documentation: "the following line: BrowserMatch bMSIE !no-gzip !gzip-only-text/html must be written instead as: BrowserMatch \bMSIE !no-gzip !gzip-only-text/html The effect of this typo is that files that are not caught by previously listed rules, such as all *.css and *.js files are never deflated for MSIE

Hello Minions! It''s *finally* here. Mongrel 1.0 RC1 for everyone to test, even the win32 folks. I managed to get everything to build on windows, including fastthread, and even cleaned up the "releases source":http://mongrel.rubyforge.org/releases/ so that it should install cleaner. Win32 will have to try and report problems, as it seems rubygems is real finicky on win32.

I''ve been getting a bunch of reports about the latest Rails "leaking" memory more than before. Please fill out this survey: 1) Have you noticed an increase in memory usage with the latest Rails 1.2? 2) Have you changed anything else in your application? a) No, really, don''t be a dumbass like the lusers you hate. Go look at your svn logs and really figure out if

Alright folks, after nearly a month of pounding and beating up the Mongrel 1.0 RC1 release we''re putting out the official 1.0.1 release. Read all about it at the (much funnier) news posting: http://mongrel.rubyforge.org/news.html For those people in a hurry, the gems should hit the mirrors and you can install using your usual commands. Refer the the above page for more help.

Is there a better way to do the following? I have data in a number of tab delimited files. I am using read.delim() to read them, in a loop. I am invoking my code on Linux Fedora 20, from the BASH command line, using Rscript. The code I'm using looks like: arguments <- commandArgs(trailingOnly=TRUE); # initialize the capped_data data.frame capped_data <- data.frame(lpar="NULL",