On Apr 14, 2005, at 6:02 PM, Jim Abramson wrote:


<excerpt><fontfamily><param>Arial</param><smaller>At some point btn
Zope 2.6.2 and 2.7.4, it seems way you set up a logfile to be used by
requestprofiler.py has changed.</smaller></fontfamily> 


<fontfamily><param>Arial</param><smaller>Now I need "debug.log" -
whats the proper way to generate one?  I've just been googling and
can't find explicit instructions about this.</smaller></fontfamily>


<fontfamily><param>Arial</param><smaller>

</smaller></fontfamily></excerpt>

The log that I think of as the "debug.log" seems to now be called the
"event log". Request profiler still needs the "trace log". You can
enable it by putting the following stanza in your zope.conf file:


<<logger trace>

        level WARN

        <<logfile>

                path $INSTANCE/log/trace.log

                format %(message)s

        <</logfile>

<</logger>


The zopectl command isn't the direct equivalent of the old z2.py. It
is a wrapper around it. (the rough equivalent of z2.py is run.py, The
zopectl program spawn something that spawns run.py) so command line
parameters added to zopectl aren't seen by zope itself.