, are you running? I'd like to get
to the bottom of this ASAP, thanks!
--
Eric Wong
___
mongrel-unicorn mailing list
mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Chris Wanstrath ch...@ozmm.org wrote:
On Tue, Oct 6, 2009 at 2:30 PM, Eric Wong normalper...@yhbt.net wrote:
Thanks. I'll take a look. Do you have any example controllers/actions
to reproduce this with so I can track this down easier? (I completely
understand if you can't share secrets
Eric Wong normalper...@yhbt.net wrote:
Chris Wanstrath ch...@ozmm.org wrote:
On Tue, Oct 6, 2009 at 2:50 PM, Eric Wong normalper...@yhbt.net wrote:
No worries, I'm working on a a reproducible test case. Can you try
and see if you're using curl's -F to POST, you _don't_ hit
Chris Wanstrath ch...@ozmm.org wrote:
On Tue, Oct 6, 2009 at 3:52 PM, Eric Wong normalper...@yhbt.net wrote:
OK, here's a workaround that should work for now. I have to hit the
road in a few minutes but will be back on a computer in a few hours.
This only affects older Rails (and I'm
minor documentation improvements.
Eric Wong (8):
Fix NEWS generation on single-paragraph tag messages
Include GPLv2 in docs
doc: make it clear contributors retain copyrights
TODO: removed Rainbows! (see rainbows.rubyforge.org)
Document the START_CTX hash contents
the above setups are valid. The important part is that
nginx must sit *somewhere* in between Unicorn and the rest of the world.
--
Eric Wong
___
mongrel-unicorn mailing list
mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel
Dusty Doris unic...@dusty.name wrote:
On Fri, Oct 9, 2009 at 6:01 PM, Eric Wong normalper...@yhbt.net wrote:
Dusty Doris unic...@dusty.name wrote:
1. Simply use mongrels upstream and let it round-robin between all
the unicorn instances on the different servers? Or, perhaps use the
fair
Mailman is now configured to munge Reply-To: to point back to
the mailing list. This might make things easier for folks
on low traffic mailing lists like ours.
---
Eric Wong normalper...@yhbt.net wrote:
Jeremy Evans jeremyeva...@gmail.com wrote:
Eric,
This and earlier replies
In short: upgrade to Rails 2.3.4 (or later)
ref: http://mid.gmane.org/20091014221552.ga30...@dcvr.yhbt.net
Note: the workaround described in the article above only made
the issue more subtle and we didn't notice them immediately.
---
Eric Wong normalper...@yhbt.net wrote:
Hi all,
I
/syswrite
because I have a very intense and long-standing distrust of luserspace
IO buffering libraries.
--
Eric Wong
___
mongrel-unicorn mailing list
mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
as the Unicorn website).
Should you ever want to access either of the sites offline, just make
sure you have RDoc 2.4.x (gem install rdoc if you're on 1.8) and run
`make doc' or `gmake doc' in the latest source tree.
--
Eric Wong
___
mongrel-unicorn mailing list
Eric Wong normalper...@yhbt.net wrote:
As I'm sure you've all heard by now, RubyForge will be moving to a
read-only state and we'll have to migrate our mailing lists somewhere.
OK, it looks like we'll be able to keep our mailing lists on RubyForge.
http://tomcopeland.blogs.com/juniordeveloper
/public_html/rm/current/config/unicorn.rb.
If you don't start in your current symlink dir, 0.94.0 also got
support for working_directory in your config file.
--
Eric Wong
___
mongrel-unicorn mailing list
mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman
Eric Wong normalper...@yhbt.net wrote:
Michael Guterl mgut...@gmail.com wrote:
cd ~/public_html/rm/current
unicorn_rails -D -E production -c config/unicorn.rb
I determined the -c config/unicorn.rb was the problem. If I change it to:
unicorn_rails -D -E production -c ~/public_html
Michael Guterl mgut...@gmail.com wrote:
On Wed, Nov 18, 2009 at 9:06 PM, Preston Marshall
pres...@synergyeoc.com wrote:
This may be a dumb question, but where can I see the error logs that are
usually displayed when unicorn is not daemonized? The production.log file
is empty in my app.
URI.parse(http://..;) supports
and pushed out the change.
I've been meaning to make a few more small documentation updates and do
a 0.95.3 release tomorrow when I'm more awake.
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http
decide which code to return).
Does it make sense? Thanks a lot.
We avoid introducing command-line options since they're unlikely to be
compatible with rackup parsing of the #\ lines in .ru files.
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn
Iñaki Baz Castillo i...@aliax.net wrote:
El Miércoles, 23 de Diciembre de 2009, Eric Wong escribió:
But again, you don't need to use DRb for this.
As I've said in other thread I want DRb to get some info related to the
application. A DRb client console could be used to check application
works for me for the two cases I explained in my previous mail.
Of course it's an optional feature (I've implemented it with -M --min-
running-time SECONDS in the options parser).
I believe the nginx grace period is hard-coded at 5 seconds, which should
be enough.
--
Eric Wong
, if you're building a Rack
app from scratch. Some frameworks already handle Content-Length for
you.
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like
Iñaki Baz Castillo i...@aliax.net wrote:
El Lunes, 28 de Diciembre de 2009, Eric Wong escribió:
Since there's absolutely no point in running Unicorn on port 80/443, you
should just avoid user switching entirely since it'll significantly
simplify your setup(s).
The problem are init
Iñaki Baz Castillo i...@aliax.net wrote:
El Lunes, 28 de Diciembre de 2009, Eric Wong escribió:
It's really awesome! I've tested it and it works great, and avoids the
sleeping stuff and a new commandlline option. Congratulations :)
The current version is actually slightly buggy
Iñaki Baz Castillo i...@aliax.net wrote:
El Lunes, 28 de Diciembre de 2009, Eric Wong escribió:
Iñaki Baz Castillo i...@aliax.net wrote:
El Lunes, 28 de Diciembre de 2009, Eric Wong escribió:
As a suggestion, could the grandparent rescue such exception and
display some kind
Iñaki Baz Castillo i...@aliax.net wrote:
El Domingo, 3 de Enero de 2010, Eric Wong escribió:
# Totally untested, stick this in your Unicorn config file and let
# us know if it works or blows up badly:
require 'syslog_logger'
class MySyslogLogger SyslogLogger
alias
paths, but some people like
non-absolute ones for various reasons. So we always ensure
stderr_path is set after working_directory is called.
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman
needed (inside the worker processes), but if you use
memcached in your app initialization code, then the socket will be
opened in the master process (which is bad).
So the safe thing would be to reconnect to your memcached servers in the
after_fork hook.
--
Eric Wong
Iñaki Baz Castillo i...@aliax.net wrote:
El Martes, 5 de Enero de 2010, Eric Wong escribió:
So I'm totally lost. However if I test my databases in before_fork then
I see N number of DB connections (N = workers num).
How are you testing the database? `` or via Ruby code?
I use Ruby
Iñaki Baz Castillo i...@aliax.net wrote:
El Miércoles, 6 de Enero de 2010, Eric Wong escribió:
Iñaki Baz Castillo i...@aliax.net wrote:
El Martes, 5 de Enero de 2010, Eric Wong escribió:
Yes, before_fork and after_fork are both called for every worker
forked.
So if I just want
to say that if there's an https *anywhere* in the
X-Forwarded-Proto chain, that rack.url_scheme should be set to
https? Because I suppose most of the time there's only one
(client-facing) proxy using https.
--
Eric Wong
___
Unicorn mailing list
Eric Wong normalper...@yhbt.net wrote:
Iñaki Baz Castillo i...@aliax.net wrote:
In your case it seems valid for me (just an opinnion) as
HTTP_X_FORWARDED_PROTO: http,https could mean that the request has been
sent
using HTTPS and an intermediary proxy has forwarded it using HTTP
some tools wanting
the pid file earlier... I'll get back to this on Tuesday.
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post
Iñaki Baz Castillo i...@aliax.net wrote:
El Lunes, 18 de Enero de 2010, Eric Wong escribió:
Iñaki Baz Castillo i...@aliax.net wrote:
El Domingo, 17 de Enero de 2010, Iñaki Baz Castillo escribió:
What about if Unicorn very quicky prepares the trap for USR2 so in case
it receives
should fix things, just keep Rack 1.0.1
installed).
I'll add this to the FAQ for now, not sure if there's a sane solution
for it...
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel
to prevent all cases of this in one
process, even in a purely C application, so we won't bother
trying.
We continue to always defer signal handling to the main loop
anyways, and signals sent to the master process will be
deferred/ignored until Unicorn::HttpServer#join is run.
---
Eric Wong
made those optimizations to Rack, too :
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
Eric Wong normalper...@yhbt.net wrote:
Travis Bell tra...@meticulo.com wrote:
Just a follow up, it looks like it was rack 1.1.0 causing the issues.
I uninstalled it, and am now using rack 1.0.1 and the error has gone
away.
Why it worked with Thin + Rack 1.1.0 and not Unicorn, still
John-Paul Bader h...@h3q.com wrote:
To counter check I just built the latest ruby from source as well and
the issue reappeared - so it happened between 26253 and tag/248
Keep in mind that 1.8.7-p248 is from the ruby_1_8_7 branch, not the
ruby_1_8 branch which contains r26253.
--
Eric Wong
it based on the EINVAL.
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
John-Paul Bader h...@h3q.com wrote:
Sorry one more:
Is this something you will address sooner or later or is this a ruby
on bsd bug?
This bug actually affects anything that writes to sockets/pipes on BSD,
not just Unicorn. So the patch should be backported to 1.8.7 upstream.
--
Eric Wong
unistd system calls.
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
to
(eventually) retry on EAGAIN.
I thought your diff was the ruby diff of r26253 and didn't realize it
was yours ;)
Actually, it's not mine, I just submitted the ticket that fixed one bug
and introduced the one you hit :)
--
Eric Wong
___
Unicorn
app_server {
server unix:/tmp/.primary fail_timeout=0;
server unix:/tmp/.backup fail_timeout=0 backup;
}
If you see lots of errors going to .primary, then you can try increasing
the backlog for that to something you're more comfortable with.
--
Eric Wong
processes, you'll need SysV/POSIX semaphores or file locks
(flock/fcntl), but you're really better off using multiple TCP client
sockets in the first place.
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman
freed.
The functions mark and free will be called from garbage
collector.
Yes, I suck at reading and can't write code properly as a result.
* http://unicorn.bogomips.org/
* mongrel-unicorn@rubyforge.org
* git://git.bogomips.org/unicorn.git
--
Eric Wong
faster :)
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
/unicorn.sock
P.S.: I might not have a chance to respond again for the next day
or so due to personal matters. Maybe somebody else on this
list can help
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org
Alex Barlow alexbarlo...@me.com wrote:
Fixed it!
Rails was considering all requests to be local. As the request was
coming from the local ip (from nginx i assume)
Awesome.
Good to know, I've been setting these headers for so long that it's
become second nature and I've forgotten about side
] ||= ENV[RACK_ENV]
require config/environment
use Rails::Rack::Static
run ActionController::Dispatcher.new
Let us know how it goes, thanks!
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn
)
Hi John,
Unicorn itself doesn't use YAML anywhere, so you're probably just
forgetting to load it somewhere in your config file:
require 'yaml'
Some servers (Mongrel, Thin) use YAML config files, so they would've
already required 'yaml' for you.
--
Eric Wong
up with a report to ruby-core/redmine
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
but can't find anything that is specific to this issue.
No worries. Also, if you leave out the -D switch, you can try
truss/strace/dtrace-ing the process if you still don't get enough
information.
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn
gha...@gmail.com wrote:
On Thu, Mar 18, 2010 at 1:40 AM, Eric Wong normalper...@yhbt.net wrote:
gha...@gmail.com wrote:
I upgraded to Unicorn 0.97.0 from 0.96.1. Unicorn starts fine, but
sending a USR2 to the 0.97.0 master launches a new master and all the
workers, but never kills the old
However, if your apps (or dependent libraries/frameworks) share any
global resources in an unintended or unsafe manner, then you won't be
able to do this. The above example is of course highly trivial.
--
Eric Wong
___
Unicorn mailing list - mongrel
Eric Wong normalper...@yhbt.net wrote:
Do the following two patches help? I've also pushed out a few
cleanups to unicorn.git and also put up a prerelease gem at:
Hi Jamie, did you get a chance to try this?
--
Eric Wong
___
Unicorn mailing list
you'll get proper HTTP/1.1 keepalive
support and you can control keepalive_timeout:
# both of these values are the defaults for unconfigured Rainbows!
Rainbows! do
use :Base
keepalive_timeout 5
end
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn
Hi Jamie, any more news on this issue? I plan on doing a minor release
later today or tomorrow with a few minor bug fixes in unicorn.git
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo
of the
proposed middleware solution.
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
inherent to Unicorn that prevents it from playing nicely
with threads. It's just not playing nicely with threaded code written
without potential fork() calls in mind.
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org
the final CRLF. This shouldn't affect
any real and RFC-compliant clients out there. Chunked requests
with trailers have always worked and continue to work the same
way.
The rest are mostly small internal cleanups and documentation
fixes. See the commit logs for full details.
--
Eric Wong
_process_client process_client
undef_method :process_client
def process_client(client)
_process_client(client)
REQ.clear
GC.start
end
end if defined?(Unicorn)
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http
this in the Unicorn config file:
Unicorn::HttpServer::START_CTX[0] = /some/path/to/bin/unicorn
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one
Eric Wong normalper...@yhbt.net wrote:
I guess I should throw this into the examples section
Added a few more comments, but the code is still the same:
http://unicorn.bogomips.org/examples/big_app_gc.rb
http://git.bogomips.org/cgit/unicorn.git/commit/?id=510a48dafc5f7e2cb618d785885395c79570821c
http://unicorn.bogomips.org/Sandbox.html
Please send patches/pull requests for any more tips you'd like to share,
including for similar tools.
Thanks to Jamie Wilkinson for the Bundler tips!
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn
Iñaki Baz Castillo i...@aliax.net wrote:
2010/5/7 Eric Wong normalper...@yhbt.net:
Underscore isn't valid for hostnames, but it is allowed in domain names
and most DNS servers will resolve them. I've personally seen websites
with underscores in their domain names in the wild[1].
Hi Eric
(somebody had a stupid autoreply on, I subscribed them)
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
, there's no chance in hell I'd use anything other than
email for bug-tracking/support here.
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one
Hi,
HTML attachments are wasteful and thus rejected from the mailing list.
On the other hand, it actually helps to include the patch itself
(inline) so it's readable without a (human) context switch :)
- Forwarded message from Pierre Baillet o...@fotonauts.com -
Subject: Fwd: Support
to block/catch/ignore those signals, so we rely on the master
process to deliver them.
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one
it is extremely unusual. We were getting it from a crappy bot.
ref:
http://mid.gmane.org/aanlktimuggcwnamcvzdvifwdf-ucw_rgyzaue7phu...@mail.gmail.com
Acked-by: Eric Wong normalper...@yhbt.net
---
ext/unicorn_http/unicorn_http.rl |9 +
test/unit/test_http_parser_ng.rb | 20
/evanphx/rubinius/issues/356
[8] - http://github.com/evanphx/rubinius/issues/347
[9] - mailto:mongrel-unicorn@rubyforge.org
[a] - mailto:unic...@bogomips.org
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org
Hongli Lai hon...@phusion.nl wrote:
On Tue, Jun 8, 2010 at 9:20 PM, Eric Wong normalper...@yhbt.net wrote:
Thanks Hongli, so this only affects people who remove the
config.ru that Rails 3 creates for them? Yikes...
No. The problem even occurs if you already have config.ru. But the
thing
Hi all,
I decided to try out the prerelease feature of Rubygems
for the first time, it seems to work...
So yes, gem install --pre unicorn if you're using Rails 3
(and probably like to type 'rm config.ru' :)
Same list of changes since v0.990.0:
Eric Wong (4):
t0300: Rails 3 test
parsing is done much
later than the current config.ru location attempt.
Hi Pierre,
Oops, definitely not wanted behavior. Unicorn should honor
working_directory with regard to config.ru. I'll start working
on a fix shortly, thanks for the report!
--
Eric Wong
Alexander Simonov a...@simonov.me wrote:
On Jun 10, 2010, at 10:38 AM, Eric Wong wrote:
And again (I seem to remember saying this months ago), any time you're
deploying, you should be paying extra attention to the app anyways.
That means testing with actual HTTP requests, not just seeing
in the child.
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
to fix it :).
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
servers. There is no need to upgrade if you're
happy with 1.0.0, but also little danger in upgrading.
There is one pedantic bugfix which shouldn't affect anyone
and small documentation updates as well.
--
Eric Wong
___
Unicorn mailing list - mongrel
the the request and response in between Unicorn and slow clients.
* http://unicorn.bogomips.org/
* mongrel-unicorn@rubyforge.org
* git://git.bogomips.org/unicorn.git
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman
a similar line in the unicorn_setup() function of
test-lib.sh
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
this, and is there a solution?
I haven't seen nor looked into this myself, but I've heard some talk of
multipart oddness in the Rack mailing list
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do
it could be a big upload
that uses all your memory.
What are you using that does request.body.to_s? Can you change it?
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote
logger.info SIGWINCH ignored because we're not daemonized
end
when :TTIN
+respawn = true
self.worker_processes += 1
when :TTOU
self.worker_processes -= 1 if self.worker_processes 0
--
Eric Wong
Richard Penwell almightylinux...@me.com wrote:
On Jul 15, 2010, at 6:40 PM, Eric Wong normalper...@yhbt.net wrote:
Richard Penwell almightylinux...@me.com wrote:
So I discovered this was a problem whereby request.body.to_s behaves
differently. I wonder if TeeStream should define to_s
Lawrence Pit lawrence@gmail.com wrote:
Hi Eric,
Confirmed. Works for me.
Thanks Lawrence, patch and test pushed up to unicorn.git
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo
-readable) /proc/$$/status to get
current memory usage.
There's also the sys-proctable gem, too, which I haven't used.
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote
recipes they can share.
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
master doesn't get affected by environment (or any other local)
changes in before_exec. before_exec only runs in the new master
process, so it can only affect the new master process (unless it sends
signals to the old master).
--
Eric Wong
___
Unicorn
libraries.
Are you starting it with home_run unicorn_rails or did you install
it system-wide?
Jeremy: would it be easier for home_run to just require the core-Ruby
classes first and then monkey patch the methods individually? I haven't
gotten a chance to look into home_run myself much.
--
Eric Wong
.
Thanks. I'd be eager to hear how it works out since this could be a
popular library very soon :) Is there a home_run mailing list I could
follow?
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman
Jeremy Evans jeremyeva...@gmail.com wrote:
On Wed, Aug 25, 2010 at 12:50 AM, Eric Wong normalper...@yhbt.net wrote:
Yeah, I figured using the home_run wrapper would be less than
ideal since it would get lost during exec upgrades and newer
versions of home_run wouldn't get picked up the same
for
your great work cleaning mongrel into a first class unix friend.
You're welcome!
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top
00:00:00 2001
From: Eric Wong normalper...@yhbt.net
Date: Wed, 15 Sep 2010 14:42:54 -0700
Subject: [PATCH] doc: update Sandbox document for Bundler
Thanks to Lawrence Pit, Jamie Wilkinson, and Eirik Dentz Sinclair.
ref: mid.gmane.org/4c8986da.7090...@gmail.com
ref: mid.gmane.org/5f1a02db-cbda-4302
://git.bogomips.org/kgio.git
http://git.bogomips.org/cgit/kgio.git
[1] - http://thread.gmane.org/gmane.comp.lang.ruby.core/30854
[2] - http://thread.gmane.org/gmane.comp.lang.ruby.core/31801
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn
Rubén Dávila ruben.grung...@gmail.com wrote:
Hi folks, I've experimented a problem while deploying my app, I've
sent the HUP signal to the master process, I've checked everything is
ok: new master and workers are spawned and the old ones are
killed(I've checked the PIDs), but the new code
to always be right,
just less bad/broken than the alternatives.
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when
@rubyforge.org
* git://git.bogomips.org/unicorn.git
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
machines with
a few hundred processors until a later release. Expect
Rainbows! to see some changes/improvements in the days to come,
too.
* http://unicorn.bogomips.org/
* mongrel-unicorn@rubyforge.org
* git://git.bogomips.org/unicorn.git
--
Eric Wong
are fixed, too.
== unicorn 1.0.2
This is the latest maintenance release of the 1.0.x series.
All users are encouraged to upgrade to 1.1.x stable series
and report bugs there.
Shortlog of changes since 1.0.1:
Eric Wong (8):
SIGTTIN works after SIGWINCH
fix delays in signal handling
-posting, quote only what you reply
to).
Despite this being a web server project, I (the project leader) strongly
dislike dealing with HTML form elements and interactive web interfaces
in general.
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn
before_fork config *should* work for you.
Let us know how it goes!
--
Eric Wong
___
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
1 - 100 of 466 matches
Mail list logo
