Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Rack Development
Home
+ new post
About this group
Join this group
log_tailer doesn't respect custom log paths
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
leigh  
View profile  
 More options Feb 25 2010, 5:31 pm
From: leigh <theschm...@gmail.com>
Date: Thu, 25 Feb 2010 14:31:14 -0800 (PST)
Local: Thurs, Feb 25 2010 5:31 pm
Subject: log_tailer doesn't respect custom log paths
Print | Individual message | Show original | Report this message | Find messages by this author
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-...

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


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Scytrin dai Kinthra  
View profile  
 More options Feb 25 2010, 8:28 pm
From: Scytrin dai Kinthra <scyt...@gmail.com>
Date: Thu, 25 Feb 2010 20:28:28 -0500
Local: Thurs, Feb 25 2010 8:28 pm
Subject: Re: log_tailer doesn't respect custom log paths
Print | Individual message | Show original | Report this message | Find messages by this author
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?

--
stadik.net

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google