Re: Debug mode

[John Poltorak <jp @ eyup . org>]

On Wed, Jun 27, 2001 at 02:24:22PM -0700, Mike Oliver wrote:
> Hello John,
> 
> > > I saw this message asked before (probably you), but did not know the
> > > answer.  I will take a stab at this since nobody else has spoken up,
> > > and say "no".  Of course, you could dig into the majordomo.pl or even
> > > the resend script to find out for sure.
> 
> You never said what you wanted to debug (majordomo? resend? wrapper?
> digest? archive? sendmail?) so it's a hard question to answer.  

I don't know what the available options are so how can I say what I want 
to debug?

There is a debug variable defined in several modules, but I have no idea 
how to use it.

> If you
> explain what the problem is that you're trying to attack then perhaps
> you'll get a more useful response.

I have a number of problems with Majordomo which I'd like to pin down.

One of them is the *triple* addition of subscriber names. This didn't use 
to happen, and maybe it only started when I upgraded PERL... but I'd like
to try and get some sort of trace of what happens when someone subscribes 
to a list. 

Another problem is that no one ever manages to UNSUBSCRIBE, even though 
the get confirmation that they have unsubscribed themselves. 

 
> > $DEBUG = $main'DEBUG;
> > 
> > ... quite near the start. 
> > 
> > Any idea what this is for or how it works?
> 
> That's the variable that controls a bunch of print output from the
> 'majordomo' script, so if you're interested in seeing what goes on as
> the 'majordomo' script deals with a message then you'd turn that
> variable on.

How?

Where does the output go?
 
> Mike.
> -- 
> mike.oliver@eng.sun.com
> 

-- 
John