unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Reopening logs - why no relative paths?
Date: Thu, 31 Mar 2011 15:02:48 -0700	[thread overview]
Message-ID: <20110331220248.GA1826@dcvr.yhbt.net> (raw)
In-Reply-To: <AANLkTimM0OV2=kRKjpB0Bj1AFMTpiwMj5H223-45fb6P@mail.gmail.com>

Matthew Kocher <mkocher@pivotallabs.com> wrote:
> We just spend a couple hours trying to figure out why sending a USR1
> signal wasn't causing unicorn to reopen logs.  Looking at the source
> reveals that only files opened with absolute paths are eligible for
> rotation, the others are silently skipped.
> We use the fairly standard practice of always logging to
> log/unicorn.error.log and creating symlinks to where we'd like the
> logs to live on individual hosts.  We'll change our configs for the
> time being, but is there a reason to not reopen the relative paths?

It's ambiguous due to directory changes[1].  It may be easier now that
we have the "working_directory" directive now, but configuration changes
also change (or unset) the "working_directory" which adds to the

We could try allowing it and see what happens, I suppose...

[1] - in my experience with writing daemons, directory changes make
      everything much harder all around.
Eric Wong
Unicorn mailing list - mongrel-unicorn@rubyforge.org
Do not quote signatures (like this one) or top post when replying

  reply	other threads:[~2011-03-31 22:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-31 17:45 Reopening logs - why no relative paths? Matthew Kocher
2011-03-31 22:02 ` Eric Wong [this message]
2011-04-01 23:15   ` Eric Wong

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:

  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=20110331220248.GA1826@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=mongrel-unicorn@rubyforge.org \


* 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).