Indeed I would second this request... It would be even better if this control could be done not only through MI commands, but also through script commands/variable. It would permit increase and decrease debug level based on script logic given a more granular control over debug info.
Edson >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:devel- >[EMAIL PROTECTED] On Behalf Of Juha Heinanen >Sent: quinta-feira, 29 de maio de 2008 01:35 >To: devel@lists.openser.org >Subject: [OpenSER-Devel] changing debug level on the fly > >while doing performance tests, i tried to look for a way to change debug >level on the fly using a mi function, but didn't find any. did i >somehow managed to miss such a mi function? description on debug >keyword in core cookbook does not mention about a way to change debug >level. > >i know that i could enclose each xlog call within an if statement test >on a shared memory variable, but that would be too way too cumbersome >and would increase the size of the cfg file considerably. > >in sems, i can change log level on the fly like this: > >sems-stats -c "set_loglevel 1" > >if there is nothing now, would it be too late to implement such a >feature before 1.4 code freeze? > >-- juha > >_______________________________________________ >Devel mailing list >Devel@lists.openser.org >http://lists.openser.org/cgi-bin/mailman/listinfo/devel _______________________________________________ Devel mailing list Devel@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/devel
