Yes, sorry, that's my error.
the debug level changed to address the debug classes.
Now it is a string parameter not an integer anymore so that you can
specify different log levels for any subclass.
like all:2 passdb:5 rpc:10
In the transition I forgot to change swat.
It's in my todo list!
I'll
sorry part of that mail got lost.
you must think i'm smoking crack...
somehow the log level parameter has gotten lost in the HEAD
from swat's option list. Thus any change in swat wipes out the logging.
brad
On Wed, 2002-07-31 at 22:36, Christopher R. Hertel wrote:
> On Thu, Aug 01, 2002 at 11:
On Thu, Aug 01, 2002 at 11:37:30AM +0930, Richard Sharpe wrote:
> On Wed, 31 Jul 2002, Bradley W. Langhorst wrote:
>
> > NULL?
> > how do i set the logging level?
>
> Ummm, debug level = x
>
> or, log level = x
... in the smb.conf, *not* in the source.
> > brad
> >
> > {"Logging Options
On Wed, 31 Jul 2002, Bradley W. Langhorst wrote:
> NULL?
> how do i set the logging level?
Ummm, debug level = x
or, log level = x
> brad
>
> {"Logging Options", P_SEP, P_SEPARATOR},
>
> {"admin log", P_BOOL, P_GLOBAL, &Globals.bAdminLog, NULL, NULL, 0},
> {"log level", P_
NULL?
how do i set the logging level?
brad
{"Logging Options", P_SEP, P_SEPARATOR},
{"admin log", P_BOOL, P_GLOBAL, &Globals.bAdminLog, NULL, NULL, 0},
{"log level", P_STRING, P_GLOBAL, NULL, handle_debug_list, NULL, 0},
{"debuglevel", P_STRING, P_GLOBAL, NULL, h
