[ic] mv_action not doing what I expect...
Sat, 02 Dec 2000 19:47:20 +0100
Otherwise, you want to debug for one or some part of the IC codes, you
can add a line like
logGlobal( "My debug-info-text " . $my-variable-to-watch);
and this will write the info into the .../interchange/error.log file.
A "tail -f .../interchange/error.log" is usefull too.
Bill Randle wrote:
> You are looking in the right place to find out what refresh does.
> Set DEBUG to 1 in one of the top level interchange.cfg files
> and restart interchange to enable debugging. Output should go
> to /tmp/<something> (used to be /tmp/mvdebug in MV4).
> P.S. The above is based on MV4; there may be slight differences inIC.
> On Dec 1, 8:52pm, Paul Stearns wrote:
> } Subject: Re: [ic] mv_action not doing what I expect...
> } Where can I find the perl script wich executes when a mv_action=refresh is
> } I really need this to be consistent across browsers.
> } When reading the perl script (a perl expert I'm not)
> /usr/lib/interchange/bin/interchange, I found an area which appears to have
> something to do with the "refresh" section. I also found lines
> } which started with "#::LogDebug..." I assumed these to be commented out
> commands which would write stuff to a log. Unfortunately I don't know where it
> would write this stuff to. I would like to
> } use these commands for debugging.
> } Is there any sort of "internals" documentation which tells what bits of code
> gets executed and when? I am fighting a steep learning curve with Interchange
> and Perl.
> } Paul
> Interchange-users mailing list