> Pete
> --
> Posted via http://www.ruby-forum.com/.
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
_
y plan, what do you guys think?
>
> Cheers,
> --
> Luis Lavena
> AREA 17
> -
> Perfection in design is achieved not when there is nothing more to add,
> but rather when there is nothing more to take away.
> Antoine de Sai
>> I wouldn't hold my breath for that patch to be incorporated in mongrel
>> though, the mongrel philosophy seems to be to be conservative in what it
>> accepts.
>
> Not speaking for the rest of the team, but I'm very much against this
> patch.
>
> ref: http://mongrel.rubyforge.org/wiki/Security
>
> --
> Eric Wong
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
__
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
ig ruby player
> or Hongli. So, test your stuff completely, then roll it out.
>
> Please report back to me if you have problems with the patch and/or if
> it works great for you so I can help some other folks out.
>
> Thanks people. Always looking out for ya.
>
> --
> A1S9-4A:
ore valuable than the blog post
>> itself.
>>
>> Regards,
>> --
>> Luis Lavena
>> AREA 17
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
__
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
n Fri, 23 May 2008 13:03:58 -0400
> "Evan Weaver" <[EMAIL PROTECTED]> wrote:
>
>> This line is for the reload signal that always says "Might not work
>> well" at startup, right? Did it used to work well? If nobody really
>> uses it might be better t
ll
> --
> Posted via http://www.ruby-forum.com/.
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
_
___
>> Mongrel-users mailing list
>> Mongrel-users@rubyforge.org
>> http://rubyforge.org/mailman/listinfo/mongrel-users
>>
>
> filipe {
> @ icewall.org
> GPG 1024D/A6BA423E
> http://filipe.icewall.org/
> }
>
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
.
>
> The good news is that "maybe" updating rubygems and recompiling mongrel
> helps with memory leaks in rails apps.
>
> Thoughts?
> -R
> OS X PPC patchlevel 111
> --
> Posted via http://www.ruby-forum.com/.
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
-1.1.4/bin/mongrel_rails:281"]
>
> This app is the beta test copy of our "intranet portal" application. It
> never has problems on the production server.
>
> For reference, the other application is referred to internally as
> "paperless-
Oh, I meant a Ruby backtrace:
http://eigenclass.org/hiki.rb?ruby+live+process+introspection
Evan
On Tue, Apr 1, 2008 at 9:55 AM, Michael Kinney <[EMAIL PROTECTED]> wrote:
> Evan Weaver wrote:
> > Gdb the stuck mongrel and force it to raise a backtrace.
>
> I had to wait fo
ported - but then I saw
> one go silent within a half hour of a restart.
>
> Any suggestions?
> --
> Posted via http://www.ruby-forum.com/.
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.or
rubyforge.org/pipermail/mongrel-users/2006-October/001847.html
>
> --------
>
> --
> Eric Wong
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
Cloudburst, LLC
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
You're right, ok. So the memory causing the OOM error isn't actually
on the Ruby heap, but it can't get freed until the opaque object gets
GC'd.
Evan
On Tue, Mar 25, 2008 at 1:20 PM, Kirk Haines <[EMAIL PROTECTED]> wrote:
> On Tue, Mar 25, 2008 at 11:02 AM, Evan Wea
n we really _need_ to, when there is
> no strong argument for them being inside of Mongrel itself. GC.start
> stuff is simple enough to put into one's own code at appropriate
> locations, or to put into a customized Mongrel handler if one needs
> it.
>
> Maybe this simply needs to be documented in the body of
...if you meant the Rails console. You say 'console' and 'server'
both; I should have read more carefully.
If you want it in the script/server STDOUT you could add something
similar to config/environment.rb.
Evan
On Mon, Mar 24, 2008 at 2:32 PM, Evan Weaver <[EMAIL PROTEC
> Posted via http://www.ruby-forum.com/.
> _______
>
>
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
Cloudburst, LLC
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
s and plugins and not all are well
> behaved and free of memory leaks. Rails itself may also have regular leaks
> from time to time and I'd prefer to have my application consistently be slow
> than randomly (and unexpectedly) be slow. The altern
nd GC costs that are
> noticable to the user during requests is a common thing for Rails
> apps, and the reason for that is bad code in Rails and not just bad
> user code, then the Rails folks should be the targets of a
> conversation on the matter. Mongrel itself, though, does
I saw that, so I mentioned gettext as the only one that stands out.
There can be more gems than just system gems though.
Evan
On Fri, Mar 21, 2008 at 1:11 PM, Kirk Haines <[EMAIL PROTECTED]> wrote:
> On Fri, Mar 21, 2008 at 10:50 AM, Evan Weaver <[EMAIL PROTECTED]> wrote:
> &g
Some things to try:
Downgrade Ruby to p111 (unlikely).
Avoid using gettext (more likely).
Are you using any RubyInline plugins or vendorized gems?
Evan
On Fri, Mar 21, 2008 at 12:50 PM, Evan Weaver <[EMAIL PROTECTED]> wrote:
> Do you have any GC patches in Ruby, use of DL, shaky C l
#x27;t have an
> immediate hypothesis, but somehow something is getting into the Ruby
> heap that isn't a recognized node type.
>
>
> Kirk Haines
>
>
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
Cloudburst, LLC
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
() and call that in socket_error() instead.
>
> Regards,
>
> Jo
>
> --
> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
>
Nice to see that some people have started editing the wiki already!
Evan
On Thu, Feb 21, 2008 at 8:53 PM, Evan Weaver <[EMAIL PROTECTED]> wrote:
> Hello Mongrels,
>
> The official Mongrel website has finally been moved to Trac, as was
> discussed long ago on t
your eyes out, and the changeset timeline and milestones, which
make it easy to keep track of ongoing development. The SVN is still
hosted on the Rubyforge project.
Anyone can make a Trac account and edit the wiki; just sign up on the site.
Thanks
Evan
--
Evan Weaver
Cloudburst
something completely foolproof is to underestimate
> the ingenuity of complete fools.
> Douglas Adams
>
>
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
e.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
Cloudburst, LLC
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
thin gc.c. It's possible that it just called
> 'cleanup' on extensions' (now old) ruby allocated objects, which are
> linked to their own malloc'ed objects and know how to clean them up.
>
> > Evan
>
> Thanks Evan.
> -Roger
> --
>
> Posted via http://
r the
> fix).
>
>
> Til
>
>
>
>
> --
> http://plazes.com/whereis/til | +49 176 20 19 51 69 | http://tils.net
>
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org
apache config
> ForensicLog /some/path/to/a/logfile.log
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
Cloudburst, LLC
_
es this, I think).
>
> It might make a difference in performance.
> Thoughts?
>
>
> [1] http://blog.pluron.com/2008/01/ruby-on-rails-i.html
> --
> Posted via http://www.ruby-forum.com/.
>
> ___
> Mongrel-users mailing list
&
to correlate to the email alerts.
>
> I do have some requests that can take a while to process (depends on
> response time from external services), so that's a valid lead.
>
> Evan Weaver wrote:
> > Make sure your Monit check interval (not sure abou the default) is
>
ponses come back in a reasonable
> amount of time.
>
> best,
> Erik Hetzner
> ;; Erik Hetzner, California Digital Library
> ;; gnupg key id: 1024D/01DB07E3
>
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforg
s (yes/no, version)
0.9.4, 0.9.2
--
Evan Weaver
Cloudburst, LLC
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
ssues with mongrel >=1.1, which we never understood,
> but after downgrading
> to 1.0.4 things are going well again. Kirk Haines looked into it, but I
> have to admit
> I never understood what the reason of the problem with newer mongrel is.
>
> Thanks to all mongrel hackers for the amazing work!
>
> Ciao,
> -Armin
>
>
>
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
Cloudburst, LLC
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
of our goals for an eventual new runner.
Evan
On Jan 3, 2008 6:48 PM, Ezra Zygmuntowicz <[EMAIL PROTECTED]> wrote:
>
> On Jan 3, 2008, at 9:45 AM, Evan Weaver wrote:
> >
> > * Framework, if any (Camping, Merb, Rails, Nitro, Ramaze, IOWA,
> > Rack...)
>
> merb,
Either is fine. If you're not comfortable sending it to the list, then
just send it to me.
Just an email reply is enough.
Evan
On Jan 3, 2008 2:52 PM, Sean Brown <[EMAIL PROTECTED]> wrote:
> On Jan 3, 2008 12:45 PM, Evan Weaver <[EMAIL PROTECTED]> wrote:
> > Hello Mon
ms (yes/no, version)
Please mention anything else about your system that's kind of weird,
and anything that's been particularly troublesome regarding mongrel
deployment.
Evan
PS. You can get some of the Ruby information via the 'tattle' gem:
$ gem install tattle --ignor
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
Cloudburst, LLC
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
rensk <[EMAIL PROTECTED]> wrote:
> On 1/2/08, Evan Weaver <[EMAIL PROTECTED]> wrote:
>
> > I think we will probably remove the Fastthread and
> > cgi_multipart_eof_fix dependencies at the same time we get 1.9
> > compatibility. Seems appropriate to me at least.
>
ave. The earlier
> patchlevels are actually kind of broken; using fastthread in that case
> works around the problems.
>
> -mental
>
>
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
>
Either way, if someone can figure out why the C/Java extensions
don't/can't refer to the same constant in the first place, that would
be sweet. I haven't had time to investigate that in detail.
Evan
On Jan 1, 2008 11:34 PM, Evan Weaver <[EMAIL PROTECTED]> wrote:
> Not ne
On Jan 1, 2008 8:46 PM, Luis Lavena <[EMAIL PROTECTED]> wrote:
> On Jan 1, 2008 4:50 AM, Evan Weaver <[EMAIL PROTECTED]> wrote:
> > I can reproduce. Can you file a ticket?
> >
>
> Then that means rubyforge picked the older file before we replaced
> with the corre
___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
Cloudburst, LLC
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
;
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
Cloudburst, LLC
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
Also, I want to reiterate that people should subscribe to the RSS
feed, where handy release announcements come directly to you.
http://mongrel.rubyforge.org/rss.xml
Evan
On Dec 29, 2007 3:31 AM, Evan Weaver <[EMAIL PROTECTED]> wrote:
> New gems are out. You can downgrade to 1.0.3 o
New gems are out. You can downgrade to 1.0.3 or you can upgrade to
1.0.5 or 1.1.3. Versions prior to 1.0.4 are not affected.
Thanks,
Evan
On Dec 28, 2007 9:22 PM, Zed A. Shaw <[EMAIL PROTECTED]> wrote:
> On Fri, 28 Dec 2007 19:28:25 -0500
> "Evan Weaver" <[EMAIL PROTECT
> the ingenuity of complete fools.
> Douglas Adams
>
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
Cloudburst, LLC
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
Also, attaching a diff with a failing test would totally rock.
Evan
On Dec 28, 2007 7:28 PM, Evan Weaver <[EMAIL PROTECTED]> wrote:
> I guess expand_path doesn't interact well with HTTP escaping.
>
> This is pretty critical, can you file a ticket against it?
>
> Evan
ues on
> Windows (I haven't checked)
>
> Also, downgrading to 1.0.3 fixes it.
> --
> Posted via http://www.ruby-forum.com/.
> _______
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
Cloudbur
gems 1.0 indexer and stopped indexing -jruby gems.
I dunno whether JRuby can install -jruby, or -java, or both. I
uploaded a gem ending in -java so we will see.
Evan
On Dec 23, 2007 12:23 AM, Evan Weaver <[EMAIL PROTECTED]> wrote:
> The remaining issue is why JRuby didn't find th
l-1.1.2
>1 gem installed
>Installing ri documentation for mongrel-1.1.2...
>Installing RDoc documentation for mongrel-1.1.2...
>
>
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyfor
t; >Luis Lavena
> >Multimedia systems
> >-
> >A common mistake that people make when trying to design
> >something completely foolproof is to underestimate
> >the ingenuity of complete fools.
> >Douglas Adams
> >___
> >Mongrel-users mailing list
> >Mongrel-users@rubyforge.org
> >http://rubyforge.org/mailman/listinfo/mongrel-users
>
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
Cloudburst, LLC
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
1)
>
> Maybe is failing in the Gem::Specification#to_yaml
> (I don't have jruby to test it).
>
> Regards,
>
> --
> Luis Lavena
> Multimedia systems
> -
> A common mistake that people make when trying to design
> something completely foolproof is to undere
http://rubyforge.org/projects/spawn/
On Dec 18, 2007 4:38 PM, Jacob Atzen <[EMAIL PROTECTED]> wrote:
> Evan Weaver wrote:
> > There's a library called Spawn, too, which is nice for doing
> > asynchronous but still request-triggered background processing. It
> > mi
k queue and out of the mongrel/rails request response cycle.
> > Something like Bj woudl help:
> >
> > http://codeforpeople.rubyforge.org/svn/bj/trunk/README
> >
> >
>
>
> ___
>
mongrel-users
> >
>
>
>
> --
> - Brian Gupta
>
> http://opensolaris.org/os/project/nycosug/
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
Cloudburst, LLC
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
wrote:
> -B
>
> http://mongrel.rubyforge.org/docs/howto.html
>
> ~Wayne
>
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-u
've installed some rails plugins on window xp,
> mongrel server didn't work.
>
> As I ran the rake task, 'rake rails:update',
> web server has worked.
>
> ## change to the root of rails project
> $ cd test5
>
> ## check the rake tasks
> $ test5> rake --tasks
>
> ## run the 'rails:update' task
> $ test5> rake rails:update
>
> If you have installed the ruby 1.8.6 from souce package,
> maybe you must be re-install all the gem plugins(rails, rake, mysql,
> ...).
>
> ref.
> -
> http://scoop.cheerfactory.co.uk/2007/11/02/upgrading-ruby-on-ubuntu-dapper/
> -
> http://wiki.ajaxstart.com/usemodj/browse.screen?Ruby_1.8.6_Source_Install
>
>
>
> --
> Posted via http://www.ruby-forum.com/.
> ___
>
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
Cloudburst, LLC
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
implications are!
>
> Thanks if you have any answers!
>
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
Cloudburst, LLC
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
Hi Mongrels,
Anyone used Packet? http://rubyforge.org/projects/packet
It's a pure-Ruby (I think) evented framework. It might offer a nice
way forward for 1.9's system threads, JRuby, and Windows, all at once.
Mongrel's green thread queue doesn't have a lot of life left in
It already has Mongrel support!
~/gems/packet-0.1.0/lib/packet_mongrel.rb
Evan
On Nov 21, 2007 10:19 AM, Evan Weaver <[EMAIL PROTECTED]> wrote:
> Hi Mongrels,
>
> Anyone used Packet? http://rubyforge.org/projects/packet
>
> It's a pure-Ruby (I think) evented framew
t; > > from c:/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.1-mswin32
> > > /bin/mongrel_rails:281
> > > from c:/ruby/bin/mongrel_rails:16:in `load'
> > > from c:/ruby/bin/mongrel_rails:16
> > > Batchvorgang abbrechen (J/N)? j
>
r: previous declaration of 'rb_mutex_synchronize' was here
> fastthread.c: In function 'wait_condvar':
> fastthread.c:626: warning: passing argument 1 of 'rb_ensure' from
> incompatible pointer type
> make: *** [fastthread.o] Error 1
>
ring what happened.
>
> Sounds like it could be a problem with gem_plugin, or interactions between
> gem_plugin and rails, or gem_plugin ,rails, mongrel, ruby 1.8.6, and ruport
> <1.0
>
> _______
> Mongrel-users mailing list
> Mon
p://lyceum.ibiblio.org
> http://blog.johnjosephbachir.org
> aim/yim/msn/jabber.org/gtalk: johnjosephbachir
> 713-494-2704
> http://jjb.cc
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> h
< 0.4.1)
>actionmailer (1.3.4 < 1.3.5)
>actionpack (1.13.4 < 1.13.5)
>json (1.0.1 < 1.1.1)
>daemons (1.0.5 < 1.0.9)
>RubyInline (3.6.2 < 3.6.5)
>activesupport (1.4.3 < 1.4.4)
>builder (2.1.1 < 2.1.2)
>hpricot (0.5.110 < 0.6)
>fastthread (1.0 < 1.0.1)
>
> from script/server:3
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
Cloudburst, LLC
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
Cloudburst, LLC
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
Yeah pulling is no problem; svnsync is made for just this purpose.
Evan
On Nov 10, 2007 6:49 PM, Andrei Maxim <[EMAIL PROTECTED]> wrote:
>
> On 11/11/07, Evan Weaver <[EMAIL PROTECTED]> wrote:
>
> >
> > Maybe we could cook up an external service that pushed ch
chieve any goal that
> is worthwhile.
> Vince Lombardi
>
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
Cloudburst, LLC
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
ngrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
Cloudburst, LLC
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
I also don't want git.
Evan
On Nov 7, 2007 11:40 PM, Luis Lavena <[EMAIL PROTECTED]> wrote:
> On Nov 8, 2007 1:37 AM, Wayne E. Seguin <[EMAIL PROTECTED]> wrote:
> > On Nov 7, 2007 11:22 PM, Evan Weaver <[EMAIL PROTECTED]> wrote:
> > > Sounds good. Let&#
e ey namespace of devjavu so it would be an
> unlimited account.
>
> -Ezra
>
>
>
> On Nov 7, 2007, at 7:32 PM, Evan Weaver wrote:
>
> > Ezra, would that be the premium devjavu account? We already have more
> > than 5 committers.
> >
> > Evan
>
Ezra, would that be the premium devjavu account? We already have more
than 5 committers.
Evan
On Nov 7, 2007 10:31 PM, Evan Weaver <[EMAIL PROTECTED]> wrote:
> Yeah... devjavu would require migrating the SVN too which is not a big
> problem. I was thinking I would use svnmirror on m
ining open ones. But Trac is only marginally better than GForge
when it comes to ticket handling :/ .
Evan
On Nov 7, 2007 10:26 PM, Luis Lavena <[EMAIL PROTECTED]> wrote:
> On Nov 8, 2007 12:08 AM, Evan Weaver <[EMAIL PROTECTED]> wrote:
> > Dear Mongrels,
> >
> >
Trac (and also migrate the bugtracker) if
noone else has opinions, but I'm sure some of you do.
What do you think?
Evan, and the Mongrel Team
--
Evan Weaver
Cloudburst, LLC
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rub
8.6 and, more importantly, gem
> 0.9.4 everything works as advertised.
>
> Sorry for the noise.
>
>
> Cheers,
>
> PA.
>
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/
or various web servers.
>
> --
> Zed A. Shaw
> - Hate: http://savingtheinternetwithhate.com/
> - Good: http://www.zedshaw.com/
> - Evil: http://yearofevil.com/
> ___
>
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/
de, they are not born. They are made by hard effort,
> which is the price which all of us must pay to achieve any goal that
> is worthwhile.
> Vince Lombardi
>
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> htt
t; ~Wayne
>
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
Cloudburst, LLC
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
n Debian, and it's at 1.0.1
> (although I plan on upgrading today/tomorrow).
>
> Greetings,
>
> --
> Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-0154 / 1451-2244
> PGP key 1024D/8BB527AF 2001-10-23
> Fingerprint: 0C79 D2D1 2C4E 9CE4 597
ongrel-users@rubyforge.org
> > http://rubyforge.org/mailman/listinfo/mongrel-users
> >
>
>
>
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
Cloudburst, LLC
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
hanks
Evan, and the Mongrel Team
--
Evan Weaver
Cloudburst, LLC
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
t;
> --
> Zed A. Shaw
> - Hate: http://savingtheinternetwithhate.com/
> - Good: http://www.zedshaw.com/
> - Evil: http://yearofevil.com/
>
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/l
way the client sees a slow connection-establishment
> > and can draw their own conclusions, including deciding how long to
> > wait or whether to retry.
> >
> > Clifford Heath, Data Constellation.
>
>
> _____
ct 29, 2007 8:09 PM, Michael Graff <[EMAIL PROTECTED]> wrote:
> That doesn't look like it's related. The snippit you sent is specific
> to FreeBSD, in that it is asking the kernel to do additional
> filtering. To me, this is an optimization.
>
> --Michael
>
>
>
k?
>
> --
> Luis Lavena
> Multimedia systems
> -
> Leaders are made, they are not born. They are made by hard effort,
> which is the price which all of us must pay to achieve any goal that
> is worthwhile.
> Vince Lombardi
>
>
Note that there is no guarantee that this is actually the issue
discussed with the above configuration. It's just an issue that has
been raised before that might be related.
Evan
On Oct 29, 2007 8:02 PM, Evan Weaver <[EMAIL PROTECTED]> wrote:
> It's a Mongrel-configured limit
>
>
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
Cloudburst, LLC
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
as a Gem
> plugin), and to configure Mongrel to use it. Plus, if you bundle it as a
> plugin, you can distribute
> it separately from the Mongrel core, so those of us who don't need it won't
> have to load code for
> program we choose not to run.
>
> ==
> Will G
mote host: Connection refused
>
>
> speedy# telnet not.flame.org 3000
> Trying 2001:4f8:fff9::1...
> Connected to not.flame.org.
> Escape character is '^]'.
> ^]
>
> This is a fairly new problem. Any ideas on what to fix?
>
> --Michael
> _
it should send the reply back to LSWS before
> > closing the socket.
> >
> > The root cause of the problem is on Mongrel side, however, LSWS should
> > fail the request after a few retries. We will implement that in our
> > 3.3 release.
> > ***
> &g
this today.
>
> --
> WBR
>
> ___
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
Cloudburst, LLC
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
f
> target_gid it was just target_id. Forcing version 1.0.3 fixes the problem.
>
> However, I'm wondering why v. 1.0.2 gets installed. Any ideas?
>
> --
> Andrei Maxim
> http://andreimaxim.ro
> ___
> Mongrel-users mailing list
>
users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
Cloudburst, LLC
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
_______
> Mongrel-users mailing list
> Mongrel-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
--
Evan Weaver
Cloudburst, LLC
___
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
Did it stop after you upgraded Mongrel? Or did you not upgrade.
On 10/27/07, Luca Reghellin <[EMAIL PROTECTED]> wrote:
>
> It worked before, than suddenly stopped... :(
>
> Evan Weaver wrote:
> > I haven't had any trouble with 0.9.5.6, but it's a valid concern.
&
1 - 100 of 136 matches
Mail list logo
