[erlang-questions] debug output from yaws
Attila Rajmund Nohl
Wed Jun 6 17:37:54 CEST 2012
2012/6/6 Steve Vinoski <vinoski@REDACTED>:
> On Wed, Jun 6, 2012 at 9:15 AM, Attila Rajmund Nohl
> <attila.r.nohl@REDACTED> wrote:
>> I'm working on an application that uses the yaws webserver. This
>> application also contains the reshd module (see
>> http://erlang.org/pipermail/erlang-questions/2001-May/003162.html), so
>> I can connect to the erlang shell of the node even if yaws was started
>> as daemon mode. My problem is: if I connect to the shell and turn on
>> tracing (using dbg), I can't see it's output, because the stdout and
>> stderr are redirected to /dev/null.
>> Is there a way to get the debug output without restarting yaws?
> Why not use dbg:trace_port/2 with dbg:tracer/2 to redirect the trace
> output to a file or to another system?
I was hoping for something simpler, so I could get not only the output
from dbg, but from io:format/2 calls too. If there's no other
solution, I have to use something like that you propose, and also
More information about the erlang-questions