In message <16486425.yxjbenq...@ralph.baldwin.cx>, John Baldwin writes:
>To be clear, you didn't turn off printing to the console, you turned off
>writing to the msglog.
I've scavenged my notes and can't find anything to explain why.
--
Poul-Henning Kamp | UNIX since Zilog Zeus
On Monday, April 06, 2015 09:11:21 PM Poul-Henning Kamp wrote:
>
> In message <2033248.eu3rhs8...@ralph.baldwin.cx>, John Baldwin writes:
>
> >I think phk@ broke this back in 70239. Before that the log() function did
> >this:
> >
> >log()
> >{
> >
> > /* log to the msg buffer */
> >
In message <552326a2.5000...@badgerio.us>, Eric Badger writes:
>> The reason was systems not running syslog having slow serial consoles.
>
>Correct me if I've misunderstood, but that doesn't seem to matter here;
>the proposed change adds logging to the message buffer but leaves
>logging
On 04/06/2015 04:11 PM, Poul-Henning Kamp wrote:
In message <2033248.eu3rhs8...@ralph.baldwin.cx>, John Baldwin writes:
I think phk@ broke this back in 70239. Before that the log() function did
this:
log()
{
/* log to the msg buffer */
kvprintf(fmt, msglogchar, ...);
On 6 April 2015 at 14:11, Poul-Henning Kamp wrote:
>
> In message <2033248.eu3rhs8...@ralph.baldwin.cx>, John Baldwin writes:
>
>>I think phk@ broke this back in 70239. Before that the log() function did
>>this:
>>
>>log()
>>{
>>
>> /* log to the msg buffer */
>> kvprintf(fmt
In message <2033248.eu3rhs8...@ralph.baldwin.cx>, John Baldwin writes:
>I think phk@ broke this back in 70239. Before that the log() function did
>this:
>
>log()
>{
>
> /* log to the msg buffer */
> kvprintf(fmt, msglogchar, ...);
>
> if (!log_open) {
> /*
On Thursday, March 26, 2015 10:20:13 PM Eric Badger wrote:
> Using log(9) when no process is reading the log results in the message
> going only to the console (contrast with printf(9), which goes to the
> console and to the kernel message buffer in this case). I believe it is
> truer to the sem
On 03/26/2015 23:20, Eric Badger wrote:
> Using log(9) when no process is reading the log results in the message
> going only to the console (contrast with printf(9), which goes to the
> console and to the kernel message buffer in this case). I believe it is
> truer to the semantics of logging for
Using log(9) when no process is reading the log results in the message
going only to the console (contrast with printf(9), which goes to the
console and to the kernel message buffer in this case). I believe it is
truer to the semantics of logging for messages to *always* go to the
message buffe
