[Rails] Re: Workling not outputting to production.log

2009-05-04 Thread Ralph Haygood

Thanks for posting this.  It really should be explained in the
Workling documentation.

On Apr 10, 3:11 am, Albert Wong 
wrote:
> Finally figured this out, and posting it incase anyone else runs into
> this issue.
>
> It has to do with logger buffers everything sent to is and does not auto
> flush in production environment.
>
> So a quick fix is to call logger.flush whenever the worker completes,
> probably a better way to do this by putting it in some after filter, but
> not sure if workling has such a filter...
> --
> Posted viahttp://www.ruby-forum.com/.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com
To unsubscribe from this group, send email to 
rubyonrails-talk+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~--~~~~--~~--~--~---



[Rails] Re: Workling not outputting to production.log

2009-04-10 Thread Tonypm

Albert,

thank you so much for this info.  I have posted this quation twice and
not received a response.

Tried it and it is the solution.

It has been irritating me for a while, but I just haven't had time to
investigate it.

Many thanks
Tonypm
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com
To unsubscribe from this group, send email to 
rubyonrails-talk+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~--~~~~--~~--~--~---



[Rails] Re: Workling not outputting to production.log

2009-04-10 Thread Albert Wong

Finally figured this out, and posting it incase anyone else runs into 
this issue.

It has to do with logger buffers everything sent to is and does not auto 
flush in production environment.

So a quick fix is to call logger.flush whenever the worker completes, 
probably a better way to do this by putting it in some after filter, but 
not sure if workling has such a filter...
-- 
Posted via http://www.ruby-forum.com/.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com
To unsubscribe from this group, send email to 
rubyonrails-talk+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~--~~~~--~~--~--~---