TRACE writes to STDIN or STDOUT?

From: Terrence Brannon
Subject: TRACE writes to STDIN or STDOUT?
Date: Fri, 04 Jan 2008 18:33:52 +0000
Message-ID: <d969e619-9598-4639-b266-86b0a9e5652b@c4g2000hsg.googlegroups.com>

Re: http://www.lispworks.com/documentation/HyperSpec/Body/m_tracec.htm#trace

The spec doesnt say anything about STDIN and STDOUT, understandably
because these are just Unix concepts?

My question:

1 - For me, TRACE output is excellent log info. If I were writing a
web app, I would like to have this info available by running tail -f
on a file. How would you do this? Of course, because a cgi program
responds via STDOUT, the trace output would have to go to another
output channel.

TRACE writes to STDERR or STDOUT? (was: Re: TRACE writes to STDIN or STDOUT?) Terrence Brannon
Re: TRACE writes to STDIN or STDOUT? Zach Beane
Re: TRACE writes to STDIN or STDOUT? Rainer Joswig

From: Terrence Brannon
Subject: TRACE writes to STDERR or STDOUT? (was: Re: TRACE writes to STDIN or 	STDOUT?)
Date: Fri, 04 Jan 2008 18:35:26 +0000
Message-ID: <40075c1c-a6ce-4ae2-84f4-1d4dc788029b@l6g2000prm.googlegroups.com>

Much better to use the the output streams in the title than one input
and one output :)

>
> My question:
>
> 1 - For me, TRACE output is excellent log info. If I were writing a
> web app, I would like to have this info available by running tail -f
> on a file. How would you do this? Of course, because a cgi program
> responds via STDOUT, the trace output would have to go to another
> output channel.

From: Zach Beane
Subject: Re: TRACE writes to STDIN or STDOUT?
Date: Fri, 04 Jan 2008 19:02:17 +0000
Message-ID: <m3ve699zye.fsf@unnamed.xach.com>

Terrence Brannon <········@gmail.com> writes:

> Re: http://www.lispworks.com/documentation/HyperSpec/Body/m_tracec.htm#trace
>
> The spec doesnt say anything about STDIN and STDOUT, understandably
> because these are just Unix concepts?
>
> My question:
>
> 1 - For me, TRACE output is excellent log info. If I were writing a
> web app, I would like to have this info available by running tail -f
> on a file. How would you do this? Of course, because a cgi program
> responds via STDOUT, the trace output would have to go to another
> output channel.

See
http://www.lispworks.com/documentation/HyperSpec/Body/v_debug_.htm. You
could do something like this:

  (setf *trace-output* (open "/var/log/trace.log" 
                             :direction :output
                             :if-exists :append))
Zach

From: Rainer Joswig
Subject: Re: TRACE writes to STDIN or STDOUT?
Date: Fri, 04 Jan 2008 18:40:17 +0000
Message-ID: <joswig-ED329E.19401704012008@news-europe.giganews.com>

In article 
<····································@c4g2000hsg.googlegroups.com>,
 Terrence Brannon <········@gmail.com> wrote:

> Re: http://www.lispworks.com/documentation/HyperSpec/Body/m_tracec.htm#trace
> 
> The spec doesnt say anything about STDIN and STDOUT, understandably
> because these are just Unix concepts?
> 
> My question:
> 
> 1 - For me, TRACE output is excellent log info. If I were writing a
> web app, I would like to have this info available by running tail -f
> on a file. How would you do this? Of course, because a cgi program
> responds via STDOUT, the trace output would have to go to another
> output channel.

Did you see that it goes to the stream which is the value of *TRACE-OUTPUT* ?

You can set this to a stream you like.

-- 
http://lispm.dyndns.org/