rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: Scytrin dai Kinthra <scytrin@gmail.com>
To: rack-devel@googlegroups.com
Subject: Re: log_tailer doesn't respect custom log paths
Date: Thu, 25 Feb 2010 20:28:28 -0500	[thread overview]
Message-ID: <5a9d52bd1002251728s7189fb4cw8799b80ec79c06fe@mail.gmail.com> (raw)
In-Reply-To: <7b7b18f7-423d-4f48-bfa7-bac9a4fc97ee@v13g2000yqv.googlegroups.com>

So, this looks like an issue with rails, unless you're having an issue
with integration and settings on the Rack side of things...
If it is the latter, would you be able to provide code or more details?

On Thu, Feb 25, 2010 at 17:31, leigh <theschmick@gmail.com> wrote:
> I am using a custom logger for my config.logger via Log4r. My log
> files use the timestamp in their name (e.g., development.
> 02-25-2010.log). The log_tailer.rb assumes that the log file name is
> the default development.log, which is a false assumption. Thus, when I
> try to start
> my server without detaching it, it crashes. Not being able to use rack
> without using the default log name seems like a bug. Shouldn't it
> check the config.log_path or config.logger?
>
> Here is a related thread I found:
>
> https://rails.lighthouseapp.com/projects/8994/tickets/2350-logtailer-ignores-configlog_path
>
> I downloaded the latest version of the rack gem though, and it does
> not seem to have incorporated the submitted patch.
>
> I see that the LogTailer class's initialize method takes an optional
> log parameter, but I'm not sure how I would modify my configuration or
> environment to get it to pick up my custom logger or if that's even
> possible.
>
> Leigh
>



-- 
stadik.net

      reply	other threads:[~2010-02-26  1:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-25 22:31 log_tailer doesn't respect custom log paths leigh
2010-02-26  1:28 ` Scytrin dai Kinthra [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-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://groups.google.com/group/rack-devel

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5a9d52bd1002251728s7189fb4cw8799b80ec79c06fe@mail.gmail.com \
    --to=rack-devel@googlegroups.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.
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).