From: Eric Wong <normalperson@yhbt.net>
To: mongrel-unicorn@rubyforge.org
Cc: Lee Hambley <leehambley@me.com>
Subject: Re: PID file ownership and group
Date: Tue, 20 Sep 2011 13:23:37 -0700 [thread overview]
Message-ID: <20110920202337.GA6965@dcvr.yhbt.net> (raw)
In-Reply-To: <FF8DE317-F98B-4D13-B8D7-95B4B922A6BF@me.com>
Lee Hambley <leehambley@me.com> wrote:
> > Also, nginx (where unicorn draws many design elements from) does not
> > change the permissions of the pid file, either.
> >
> >> Of course this is somewhat academic, as one must be root to signal the
> >> process anyway, but I'll cross that particular bridge when I come to
> >> it!
> >
> > Yeah, there's no point in knowing it unless you can send signals to it.
> Surely though, with the pid being root:root when started via upstart
> (and the restrictive u+rwx/g+rwx/o-) permissions enforced by my umask,
> it would still make sense to own the pid to `unicorn:projectname` -
> given that you can signal your own processes, then the "unicorn" user
> should be able to read the pid?
Not really, the pid file is only for the master process. The master
always stays as the user it is started as (root in your case). Only the
worker processes have their user:group changed and they can't signal the
master after the change.
> (Although, that said, most implementations I have seen of "monitors"
> for unicorn seem to use `ps` to get the pid, which does seem somewhat
> wasteful)
Strange, wouldn't the monitors /not/ daemonize and thus be able to use
the pid of the process they started?
> Thanks for getting back to me so quickly on here Eric, with Github I'd
> almost forgotten that mailing lists work!
No problem. Signups/logins/passwords bother me, and I also dislike
99.999% of HTML, images, and JavaScript on the web; so I'll be sticking
to mailing lists :)
--
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
prev parent reply other threads:[~2011-09-20 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 8:18 PID file ownership and group Lee Hambley
2011-09-20 18:03 ` Eric Wong
[not found] ` <FF8DE317-F98B-4D13-B8D7-95B4B922A6BF@me.com>
2011-09-20 20:23 ` Eric Wong [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=20110920202337.GA6965@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=leehambley@me.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).