From: Lawrence Pit <lawrence.pit@gmail.com>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: [PATCH] Show the current working directory in the proc title
Date: Tue, 06 Jul 2010 12:18:21 +1000 [thread overview]
Message-ID: <4C32926D.5080400@gmail.com> (raw)
In-Reply-To: <20100705233439.GA28789@dcvr.yhbt.net>
The +after_fork+ doc mentions "generally there's no reason to start
Unicorn as a priviledged user".
"generally" that may be true, I'd still recommend to run each app as a
dedicated user.
The added bonus is that it makes it most obvious in ps(1) listings which
app a unicorn process belongs to as 'user' is usually mentioned first.
On small terminals the value of --config-file could easily be cut off at
the right, still leaving you in the dark.
Lawrence
> Jeremy Evans <jeremyevans0@gmail.com> wrote:
>
>> I see in the NEWS entry for 0.95.1 that you do recommend an absolute
>> path for the -c/--config-file option, but it may be beneficial to
>> mention this in the man page or other parts of the documentation.
>>
>
> Agreed, thanks Jeremy!
>
> >From d7695c25c5e3b1c90e63bf15a5c5fdf68bfd0c34 Mon Sep 17 00:00:00 2001
> From: Eric Wong <normalperson@yhbt.net>
> Date: Mon, 5 Jul 2010 23:14:40 +0000
> Subject: [PATCH] doc: recommend absolute paths for -c/--config-file
>
> Suggested-by: Jeremy Evans
> ref: http://mid.gmane.org/AANLkTintT4vHGEdueuG45_RwJqFCToHi5pm2-WKDSUMz@mail.gmail.com
> ---
> Documentation/unicorn.1.txt | 3 +++
> Documentation/unicorn_rails.1.txt | 7 +++++--
> 2 files changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/unicorn.1.txt b/Documentation/unicorn.1.txt
> index 24df7ab..c20a570 100644
> --- a/Documentation/unicorn.1.txt
> +++ b/Documentation/unicorn.1.txt
> @@ -36,6 +36,9 @@ with rackup(1) but strongly discouraged.
> implemented as a Ruby DSL, so Ruby code may executed.
> See the RDoc/ri for the *Unicorn::Configurator* class for the full
> list of directives available from the DSL.
> + Using an absolute path for for CONFIG_FILE is recommended as it
> + makes multiple instances of Unicorn easily distinguishable when
> + viewing ps(1) output.
>
> -D, \--daemonize
> : Run daemonized in the background. The process is detached from
> diff --git a/Documentation/unicorn_rails.1.txt b/Documentation/unicorn_rails.1.txt
> index 267e425..f426b07 100644
> --- a/Documentation/unicorn_rails.1.txt
> +++ b/Documentation/unicorn_rails.1.txt
> @@ -34,8 +34,11 @@ as much as possible.
> -c, \--config-file CONFIG_FILE
> : Path to the Unicorn-specific config file. The config file is
> implemented as a Ruby DSL, so Ruby code may executed.
> - See the RDoc/ri for the *Unicorn::Configurator* class for the
> - full list of directives available from the DSL.
> + See the RDoc/ri for the *Unicorn::Configurator* class for the full
> + list of directives available from the DSL.
> + Using an absolute path for for CONFIG_FILE is recommended as it
> + makes multiple instances of Unicorn easily distinguishable when
> + viewing ps(1) output.
>
> -D, \--daemonize
> : Run daemonized in the background. The process is detached from
>
_______________________________________________
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
prev parent reply other threads:[~2010-07-06 2:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 20:50 [PATCH] Show the current working directory in the proc title Jeremy Evans
2010-07-02 22:29 ` Eric Wong
2010-07-02 22:50 ` Jeremy Evans
2010-07-05 23:34 ` Eric Wong
2010-07-06 2:18 ` Lawrence Pit [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=4C32926D.5080400@gmail.com \
--to=lawrence.pit@gmail.com \
--cc=mongrel-unicorn@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://yhbt.net/unicorn.git/
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).