* Logging
@ 2009-11-05 23:18 Dylan Stamat
2009-11-05 23:49 ` Logging Eric Wong
0 siblings, 1 reply; 2+ messages in thread
From: Dylan Stamat @ 2009-11-05 23:18 UTC (permalink / raw)
To: mongrel-unicorn
Is there a standard approach for logging when using unicorn_rails?
Is it just a matter of specifying std_err/std_out, or setting the
logger in a unicorn.rb?
Thanks!
==
Dylan
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Logging
2009-11-05 23:18 Logging Dylan Stamat
@ 2009-11-05 23:49 ` Eric Wong
0 siblings, 0 replies; 2+ messages in thread
From: Eric Wong @ 2009-11-05 23:49 UTC (permalink / raw)
To: unicorn list
Dylan Stamat <dstamat@elctech.com> wrote:
> Is there a standard approach for logging when using unicorn_rails?
> Is it just a matter of specifying std_err/std_out, or setting the logger
> in a unicorn.rb?
Both work, I think most folks just set their stderr/stdout_paths and
leave logger as-is unless they're logging to syslog or a network device.
Unicorn itself doesn't log a lot, but you can use Rack::CommonLogger or
Clogger into your Rails/Rack middleware stack to do request logging.
Any File objects with sync=true and opened with the append flag will get
reopened with the USR1 signal including the log files Rails sets up
by default.
--
Eric Wong
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-11-05 23:49 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-11-05 23:18 Logging Dylan Stamat
2009-11-05 23:49 ` Logging Eric Wong
Code repositories for project(s) associated with this public inbox
https://yhbt.net/unicorn.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).