unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Jamie Wilkinson <jamie@tramchase.com>
To: mongrel-unicorn@rubyforge.org
Subject: Re: mongrel_proctitle like support in Unicorn
Date: Thu, 17 Jun 2010 22:22:33 +0000 (UTC)	[thread overview]
Message-ID: <loom.20100618T002015-365@post.gmane.org> (raw)
In-Reply-To: 944a03770912021404s189a3686sb8b024a21d5a7c7a@mail.gmail.com

Michael Guterl <mguterl <at> gmail.com> writes:

> On Wed, Dec 2, 2009 at 4:52 PM, Justin Hahn <jhahn <at> rbmtechnologies.com>
> > Before I go off ans try cutting my own horrible monkey patch to
> > unicorn, has anyone tried implementing something like
> > mongrel_proctitle for Unicorn?

> There's some rack middleware out there, RackProctitle, which provides
> this functionality.  I have not used it with Unicorn, but I don't see
> why it wouldn't work.
> http://coderack.org/users/arya/entries/3-rack-proctitle

FWIW this doesn't seem to work out-of-box with Unicorn. Eric, do you know
offhand if it's possible to use middleware to call unicorn's proc_name? I'd love
to be able to watch what my unicorns are doing in realtime

Slightly related -- is it also possible to interrogate the current size of a
socket's backlog? (is this what Raindrops is for? It doesn't work out of box on
my mac, but I'd see about getting it working if it did)

Congrats on 1.0

Unicorn mailing list - mongrel-unicorn@rubyforge.org
Do not quote signatures (like this one) or top post when replying

  reply	other threads:[~2010-06-17 22:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-02 21:52 mongrel_proctitle like support in Unicorn Justin Hahn
2009-12-02 22:04 ` Michael Guterl
2010-06-17 22:22   ` Jamie Wilkinson [this message]
2010-06-17 23:21     ` Eric Wong
2010-06-22 23:14       ` Jamie Wilkinson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20100618T002015-365@post.gmane.org \
    --to=jamie@tramchase.com \
    --cc=mongrel-unicorn@rubyforge.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).