unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Alex Sharp <ajsharp@gmail.com>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Cc: Pai-Hung Chen <phc@zestcash.com>
Subject: Re: How to automate the restarting of Unicorn?
Date: Sun, 9 Oct 2011 16:31:42 -0700	[thread overview]
Message-ID: <D0C8FD0B85DE4305A1EC0EE8B872A1A7@gmail.com> (raw)
In-Reply-To: <CA+rii7H2gNdoWipzrhbgTu0G4H+3c9pS-PqA1jO-Cn-uGSsHxQ@mail.gmail.com>

On Friday, October 7, 2011 at 8:20 PM, Pai-Hung Chen wrote:
> My question is: By the time the "before_exec" hook is executed, is it
> guaranteed that unicorn.pid.oldbin ahas lready created (otherwise we
> have a racing condition here)? Or is there a better way to achieve
> what I want?
I'm not 100% positive, but about 98% -- yes, you can count on the fact that the *.oldbin file will exist on disk before the before_exec block is executed. Eric can confirm this, but I've never had a problem with it... 
> 
> Please Cc me as I am not on the mailing list.
> 
> Please also let me know if there is a better place to ask this question.
You're in the right place -- this is a pretty active mailing list :)

-- 
Alex Sharp

github.com/ajsharp
twitter.com/ajsharp
alexjsharp.com

_______________________________________________
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:[~2011-10-10  0:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-08  3:20 How to automate the restarting of Unicorn? Pai-Hung Chen
2011-10-09 23:31 ` Alex Sharp [this message]
2011-10-10  6:04   ` Devin Ben-Hur
2011-10-10 20:34     ` Pai-Hung Chen
2011-10-10 21:27       ` Eric Wong
2011-10-10 22:18         ` Pai-Hung Chen

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=D0C8FD0B85DE4305A1EC0EE8B872A1A7@gmail.com \
    --to=ajsharp@gmail.com \
    --cc=mongrel-unicorn@rubyforge.org \
    --cc=phc@zestcash.com \
    /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).