From: Eric Wong <firstname.lastname@example.org>
To: unicorn list <email@example.com>
Date: Tue, 17 Aug 2010 19:45:40 -0700 [thread overview]
Message-ID: <20100818024540.GA29950@dcvr.yhbt.net> (raw)
Jimmy Soho <firstname.lastname@example.org> wrote:
> > Hi Jimmy, Are you deploying with Capistrano and you originally started
> > Unicorn in a working_directory that no longer exists on the filesystem?
> > Under Linux, you can check the working directory of any process
> > with `ls -l /proc/$PID/cwd`
> Ah! Yes. I use Capistrano, and it pruned releases. But definitely
> /after/ a new version was deployed.
> What I don't understand then though is that I have this in my unicorn
> config file:
> working_directory "/srv/app1/current"
> How could the new master / workers still be pointing to the old
> directory? Isn't what this working_directory directive is for?
In your Capistrano deploy tasks, do you create/update the current
symlink before you send USR2? You should have the symlink updated
before sending USR2..
Other folks here may have more experience with Capistrano+Unicorn,
maybe they have portable recipes they can share.
Unicorn mailing list - email@example.com
Do not quote signatures (like this one) or top post when replying
next prev parent reply other threads:[~2010-08-18 2:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 0:02 ` Jimmy Soho
2010-08-18 1:14 ` Eric Wong
2010-08-18 2:23 ` Jimmy Soho
2010-08-18 2:45 ` Eric Wong [this message]
2010-08-18 3:39 ` Jimmy Soho
2010-08-18 7:14 ` Eric Wong
2010-08-18 13:20 ` Jimmy Soho
2010-08-18 23:34 ` Eric Wong
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:
List information: https://yhbt.net/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).