Update of /export/home/ntop/ntop
In directory jabber:/tmp/cvs-serv16477

Modified Files:
        address.c admin.c globals-core.h globals-defines.h 
        globals-structtypes.h graph.c hash.c initialize.c leaks.c 
        main.c netflow.c ntop.c ntop_win32.c pbuf.c plugin.c 
        pluginSkeleton.c report.c reportUtils.c sessions.c ssl.c 
        util.c vendor.c webInterface.c xmldump.c 
Log Message:

This patch rationalizes (ha!) the usage of traceEvent() in ntop.

I've arbitrarily defined a couple of new CONST_TRACE_EVENT_xxxx values
and redefined some of the old ones, with the following meaings:

     -1 - CONST_TRACE_EVENT_ALWAYSDISPLAY
       The very few messages you want to display without fail (e.g. copyright).

     0 - CONST_TRACE_EVENT_FATALERROR
       ntop encountered a problem which prevents it from continuing.

     1 - CONST_TRACE_EVENT_ERROR
       ntop encountered a problem.  Processing will continue, but
       features/functions may be degraded or disabled.

     2 - CONST_TRACE_EVENT_WARNING
       ntop encountered something that isn't right.  Processing
       continues with a reasonable assumption made.

     3 - CONST_TRACE_EVENT_INFO
       detailed messages about the startup and operation of ntop.

     4 - CONST_TRACE_EVENT_NOISY
       Very detailed messages about ntop during startup and purge, etc.

     5 - CONST_TRACE_EVENT_DETAIL
       Equivalent to CONST_TRACE_EVENT_NOISY, but all records
       written to stdout (i.e. not logging) will have a file/line
       stamp.

Note that "**FATAL_ERROR**", "**ERROR**" and "**WARNING**" are automatically
prepended to the text for their respective messages.

Up til now, only 1, 2 and 3 were actually used.  CONST_TRACE_EVENT_NOISY
gives us the ability to have very detailed messages during startup which
don't normally appear, but don't require a #define and recompile to expose.



There's a few other minor fixes burried in there - just too much trouble to
split them out.  LSWATCH is the only one of note - fixed a problem w/ multiple
interfaces - where it would just ignore data.

the -t | --log-level parameter minimum is 1 (old code didn't check that,
which allowed -t -1 to turn off all logging.  You can't turn off FATALERROR.


-----Burton (ref 229)



_______________________________________________
Ntop-dev mailing list
[EMAIL PROTECTED]
http://listgateway.unipi.it/mailman/listinfo/ntop-dev

Reply via email to