Who can explain to me the differences between the different log levels of isapi_redirect ? I can't find nothing about it on official web site and documentation. The different log levels are : - debug - info - error - emerg Thanks
"Lambuz" wrote in message news:1147420184.033848.69570@u72g2000cwu.googlegroups.com... > Who can explain to me the differences between the different log levels > of isapi_redirect ? > > I can't find nothing about it on official web site and documentation. > > The different log levels are : > - debug > - info > - error > - emerg You can sort of guess what each log level those by its name. "debug" is used for when the program isn't behaving the way it's supposed to, and the developers of the program want to know why. It might dump the contents of variables, or notify entry and exit of methods, for example. "info" is just to inform the user about what the program is doing. "error" is used when something bad happens, and "emerg[ency]" is for when something REALLY bad happens. Perhaps with "error", the program can try to recover, but it the user or administrator should fix something soon. With "emerg", the program will probably halt then and there. - Oliver
Thanks for your answer but I think on it there are too much supposition and perhaps, I need an answer sure at 100% and a clear explanation of waht is logging in each level.
isapi_redirect is Open Source, so I recommend you read the source code and figure it out to be 100% certain. And when you finish, please publish it as documentation so that no one has to do it again. Otherwise, you are only assuming and supposing that the log level works in a certain way without validating it actually works without bugs. -- //David IIS http://blogs.msdn.com/David.Wang This posting is provided "AS IS" with no warranties, and confers no rights. // "Lambuz" wrote in message news:1147464189.262907.32640@j33g2000cwa.googlegroups.com... > Thanks for your answer but I think on it there are too much supposition > and perhaps, I need an answer sure at 100% and a clear explanation of > waht is logging in each level. >
