Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
ISC Open Source Projects
Kea
Commits
27442da4
Commit
27442da4
authored
Dec 11, 2012
by
Jelte Jansen
Browse files
[2445] Revert "Remove setLogLevel(TRACE) in createBufferAppender"
This reverts commit
3f9c7bb8
.
parent
3f9c7bb8
Changes
2
Hide whitespace changes
Inline
Side-by-side
src/lib/log/logger_manager_impl.cc
View file @
27442da4
...
...
@@ -145,6 +145,9 @@ LoggerManagerImpl::createBufferAppender(log4cplus::Logger& logger) {
log4cplus
::
SharedAppenderPtr
bufferapp
(
new
internal
::
BufferAppender
());
bufferapp
->
setName
(
"buffer"
);
logger
.
addAppender
(
bufferapp
);
// Since we do not know at what level the loggers will end up
// running, set it to the highest for now
logger
.
setLogLevel
(
log4cplus
::
TRACE_LOG_LEVEL
);
}
// Syslog appender.
...
...
src/lib/log/tests/buffer_logger_test.cc
View file @
27442da4
...
...
@@ -22,7 +22,7 @@ using namespace isc::log;
namespace
{
void
usage
()
{
std
::
cout
<<
"Usage: buffer_logger_test [-n
v
]"
<<
std
::
endl
;
std
::
cout
<<
"Usage: buffer_logger_test [-n]"
<<
std
::
endl
;
}
}
// end unnamed namespace
...
...
@@ -52,10 +52,10 @@ main(int argc, char** argv) {
}
}
// Note, level is
set t
o DEBUG
here, but back to INFO
//
in process(), so when flushing to stdout (-n), the DEBUG
//
message should show up
initLogger
(
"buffertest"
,
isc
::
log
::
DEBUG
,
99
,
NULL
,
true
);
// Note, level is
INFO, s
o DEBUG
should normally not show
//
up. Unless process is never called (at which point it
//
will end up in the dump at the end).
initLogger
(
"buffertest"
,
isc
::
log
::
INFO
,
0
,
NULL
,
true
);
Logger
logger
(
"log"
);
// No need for file interprocess locking in this test
logger
.
setInterprocessSync
(
new
isc
::
util
::
InterprocessSyncNull
(
"logger"
));
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment