Jeremy Evans <[email protected]> wrote:
> This is helpful if you run a server with many web apps in separate
> directories all running unicorn, as it allows you to easily see
> which processes are tied to which app.
Hi Jeremy,
I recommend using absolute paths with -c/--config-file and allowing
users to opt-in to it (everybody should be using a Unicorn config
file in production).
Having an extra working directory path in there hurts people on smaller
terminals[1]. With -c, users have more control of what their
command-line looks like without having something forced on them.
I can't see myself accepting this patch right now for the above reasons.
On the other hand, I don't see any reason to alter the way proc_name is
used in the future, so monkey patching here is fine.
I'm sure there'll always be folks that will want something different in
$0 (as evidenced by Rack::Contrib::ProcTitle and like).
[1] - I try to be considerate of on-call folks working from mobile
phones or netbooks and/or bad net connections. There's even
a test in test_exec.rb to ensure the help output text can fit
in standard 80x24 ANSI terminals. Personally, I refuse to use
a terminals wider than 80 columns (actually, I would've
preferred the world standardized on a 64-column wrap)
--
Eric Wong
_______________________________________________
Unicorn mailing list - [email protected]
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
