Re: log(9) bug? or feature?

2001-10-04 Thread Kazutaka YOKOTA
Sorry, >2) log() in rev 1.67 or later > > log() ---> the log buffer ONLY This should be 2) log() in rev 1.67 or later log() ---> the log buffer ONLY, if a process is reading it log() ---> /dev/console ONLY, if no process is reading the log buffer Kazu To Unsubscribe: sen

Re: log(9) bug? or feature?

2001-10-04 Thread Kazutaka YOKOTA
>>In rev 1.67 and later, the message goes to the log buffer only if a >>process is reading the log buffer. If no process is reading, the >>message goes to the console ONLY, and it is not put into the log >>buffer. This behavior is inconsistent with the above comment. Is this >>a bug introduced i

Re: log(9) bug? or feature?

2001-10-04 Thread Garrett Wollman
< said: > Actually, I *desperately* want a way to turn this off. I agree (somewhat less emphatically) and even filed a PR about a related issue. -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: log(9) bug? or feature?

2001-10-04 Thread Peter Wemm
Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, Kazutaka Y OK > OTA writes: > > >In rev 1.67 and later, the message goes to the log buffer only if a > >process is reading the log buffer. If no process is reading, the > >message goes to the console ONLY, and it is not put into the l

Re: log(9) bug? or feature?

2001-10-04 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Kazutaka YOK OTA writes: >In rev 1.67 and later, the message goes to the log buffer only if a >process is reading the log buffer. If no process is reading, the >message goes to the console ONLY, and it is not put into the log >buffer. This behavior is inconsistent