unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: "Iñaki Baz Castillo" <ibc@aliax.net>
To: mongrel-unicorn@rubyforge.org
Subject: Re: Why "--pid" is deprecated?
Date: Fri, 25 Dec 2009 23:21:23 +0100	[thread overview]
Message-ID: <200912252321.23817.ibc@aliax.net> (raw)
In-Reply-To: <20091224191735.GA14191@dcvr.yhbt.net>

El Jueves, 24 de Diciembre de 2009, Eric Wong escribió:
> > Which is the real advantage of using "pid" directive in config file
> > rather  than "--pid"?
> 
> Not much, pid files suck either way.  Sadly there aren't many other
> options that's universally used/accepted.

Ubuntu upstart system (now also adopted by Debian) is a great improvement over 
classic init system as it behaves as a daemon which already knows the PID 
number used for each service (so it doesn't need to look for it in a file).
However I haven't experiment with upstart yet.


> Using ENV["UNICORN_PID"] could be an option in the config file if you
> want to share it between the config and init script.

The problem is that config file is usually a XML/INI/YAML/Ruby file, while a 
common init script is writen in Bash (99% of times), so reading a config 
parameter from the init script involves dirty parsing and so... :(

Well, I agree that using PID file is ugly and not cool at all, but it's widely 
used and it's what we have now :)




-- 
Iñaki Baz Castillo <ibc@aliax.net>
_______________________________________________
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


      reply	other threads:[~2009-12-25 22:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-24 13:36 Why "--pid" is deprecated? Iñaki Baz Castillo
2009-12-24 19:17 ` Eric Wong
2009-12-25 22:21   ` Iñaki Baz Castillo [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=200912252321.23817.ibc@aliax.net \
    --to=ibc@aliax.net \
    --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).