rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / code / Atom feed
* log_tailer doesn't respect custom log paths
@ 2010-02-25 22:31 leigh
  2010-02-26  1:28 ` Scytrin dai Kinthra
  0 siblings, 1 reply; 2+ messages in thread
From: leigh @ 2010-02-25 22:31 UTC (permalink / raw)
  To: Rack Development

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: log_tailer doesn't respect custom log paths
  2010-02-25 22:31 log_tailer doesn't respect custom log paths leigh
@ 2010-02-26  1:28 ` Scytrin dai Kinthra
  0 siblings, 0 replies; 2+ messages in thread
From: Scytrin dai Kinthra @ 2010-02-26  1:28 UTC (permalink / raw)
  To: rack-devel

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2010-02-26  1:28 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-02-25 22:31 log_tailer doesn't respect custom log paths leigh
2010-02-26  1:28 ` Scytrin dai Kinthra

Code repositories for project(s) associated with this inbox:

	https://80x24.org/mirrors/rack.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).