Backgroundrb devel - May 2008 - Storing worker driven rails logging in worker log file?

Hi all,
	We have a few workers that kick off at scheduled intervals or to do  
some user driven long running tasks asynchronously.  At the moment  
when the workers start working with AR model objects, all of the Rails  
logging ends up in the default rails environment log file  
(develolopment/prodiction.log).
	Does anyone have any tips for getting rails to append to a separate  
worker log file?  We''d like to keep the rails logging in a separate  
file so that we can easily find it later - mixed into the main rails  
log it can be difficult to figure out which log entries are as a  
result of controller actions doing their work and which are being  
driven by workers.

Thanks for any tips,

John.

I don''t know the answer to this, but I''d second it and ask, Is
this
why there is a 150M logging worker???

On May 2, 2008, at 2:23 PM, John O''Shea wrote:
> Hi all,
> 	We have a few workers that kick off at scheduled intervals or to do  
> some user driven long running tasks asynchronously.  At the moment  
> when the workers start working with AR model objects, all of the  
> Rails logging ends up in the default rails environment log file  
> (develolopment/prodiction.log).
> 	Does anyone have any tips for getting rails to append to a separate  
> worker log file?  We''d like to keep the rails logging in a
separate
> file so that we can easily find it later - mixed into the main rails  
> log it can be difficult to figure out which log entries are as a  
> result of controller actions doing their work and which are being  
> driven by workers.
>
> Thanks for any tips,
>
> John.
>
> _______________________________________________
> Backgroundrb-devel mailing list
> Backgroundrb-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/backgroundrb-devel