Always send log(9) messages to the message buffer.
It is truer to the semantics of logging for messages to *always* go to the message buffer, where they can eventually be collected and, in fact, be put into a log file. This restores the behavior prior to r70239, which seems to have changed it inadvertently. Submitted by: Eric Badger <eric@badgerio.us> Reviewed by: jhb Approved by: kib (mentor) Obtained from: Dell Inc. MFC after: 1 week
This commit is contained in:
parent
4b8175ee8f
commit
c207ff9319
@ -67,7 +67,8 @@ The
|
||||
.Fn log
|
||||
function sends the message to the kernel logging facility, using
|
||||
the log level as indicated by
|
||||
.Fa pri .
|
||||
.Fa pri ,
|
||||
and to the console if no process is yet reading the log.
|
||||
.Pp
|
||||
Each of these related functions use the
|
||||
.Fa fmt
|
||||
|
@ -295,7 +295,7 @@ log(int level, const char *fmt, ...)
|
||||
va_list ap;
|
||||
|
||||
va_start(ap, fmt);
|
||||
(void)_vprintf(level, log_open ? TOLOG : TOCONS, fmt, ap);
|
||||
(void)_vprintf(level, log_open ? TOLOG : TOCONS | TOLOG, fmt, ap);
|
||||
va_end(ap);
|
||||
|
||||
msgbuftrigger = 1;
|
||||
|
Loading…
Reference in New Issue
Block a user