Hi~
On Jan 17, 2007, at 11:06 PM, Surendra Singhi wrote:
Hi,
First of all thanks everyone for their responses.
On 1/18/07, Ezra Zygmuntowicz [EMAIL PROTECTED] wrote:
Some linux distros have weird reporting of processes. I
have seen it
where top or ps will report 3 mongrels
On Jan 18, 2007, at 12:28 PM, Joey Geiger wrote:
Is mongrel not releasing the memory used for these operations? I need
to use send_file to stream some static images (4k max) (approved,
declined, etc) which rails then turns into new cached images. This
allows a group of people to get the
I'm interested in trying ImageScience but I can't get FreeImage, the
processing lib, to build on MacOS X 10.4 (Intel). Has anyone had luck?
I tried building from source and using DarwinPorts, both no dice:
gonzo:~/Unix/Sources/imagescience_stuff/FreeImage hunter$ sudo port
install freeimage
It looks like I got too creative in 0.6.1 and consequently ran afoul of
a bug in the Ruby interpreter. 0.6.2 works around the bug and should be
entirely stable at this point.
Thanks to Young Hyun for his help in coming up with test cases.
== what?
fastthread is a Ruby library which provides a
Sorry, for those of us that don't know, how does this relate to Mongrel?
I'm not really clear on that from your message.
Sounds cool though.
On Jan 18, 2007, at 4:51 PM, MenTaLguY wrote:
It looks like I got too creative in 0.6.1 and consequently ran
afoul of
a bug in the Ruby interpreter.
On 1/18/07, Hunter Hillegas [EMAIL PROTECTED] wrote:
Sorry, for those of us that don't know, how does this relate to Mongrel?
I'm not really clear on that from your message.
Sounds cool though.
Fastthread is used in Mongrel, I believe, to avoid some memory leaks w/i Ruby.
On Thu, 2007-01-18 at 17:02 -0800, Hunter Hillegas wrote:
Sorry, for those of us that don't know, how does this relate to Mongrel?
I'm not really clear on that from your message.
fastthread resolves the memory problems that Mongrel has when using
stdlib's Mutex. It's actually a dependency
Filipe dijo [Mon, Jan 15, 2007 at 11:29:39AM -0200]:
the Gentoo method isnt perfect - it fails in the inverse scenario
where youve installed everything via gems, then want to install
something through portage that depends on installed gems (stuff
gets reinstalled). the other problem is
Got it, thanks. So, we should upgrade our fastthread to your latest
version then, right?
On Jan 18, 2007, at 5:16 PM, MenTaLguY wrote:
Sorry, for those of us that don't know, how does this relate to
Mongrel?
I'm not really clear on that from your message.
fastthread resolves the memory
On Jan 18, 2007, at 5:02 PM, Hunter Hillegas wrote:
Sorry, for those of us that don't know, how does this relate to
Mongrel?
I'm not really clear on that from your message.
Sounds cool though.
Hi Hunter,
Read the following
Zed A. Shaw dijo [Fri, Jan 12, 2007 at 10:07:16AM -0800]:
I finally have time to answer this...
I don't ;-) I'm in the middle of a high workload cycle - Anyway,
thanks to Filipe for finally posting this. He has been pestering me
over and over to upload my work to the Debian SVN repository so
Chad Woolley dijo [Mon, Jan 15, 2007 at 01:15:33PM -0700]:
I imagine that what is said will reduce down to something like this:
Provide a patch that retains the ability to selectively require
certain versions or version ranges, yet provides the version
specification freedom that you think
On Thu, 2007-01-18 at 17:28 -0800, Hunter Hillegas wrote:
Got it, thanks. So, we should upgrade our fastthread to your latest
version then, right?
Highly, highly recommended, yes. Versions earlier than 0.6 won't work
with the newest RubyGems, and 0.6.2 is the first really stable 0.6.x.
Thanks Jason, I missed that the first time around.
Hunter
On Jan 18, 2007, at 5:10 PM, Jason A. Hoffman wrote:
On Jan 18, 2007, at 5:02 PM, Hunter Hillegas wrote:
Sorry, for those of us that don't know, how does this relate to
Mongrel?
I'm not really clear on that from your message.
14 matches
Mail list logo
