Date: Fri, 24 Jan 2003 22:30:02 -0800 (PST) From: Eugene Grosbein <eugen@grosbein.pp.ru> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/46955: fxp(4) driver pollute logs and console with timeout messages Message-ID: <200301250630.h0P6U2PD061445@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/46955; it has been noted by GNATS. From: Eugene Grosbein <eugen@grosbein.pp.ru> To: bug-followup@freebsd.org Cc: Doug Barton <dougb@freebsd.org> Subject: Re: kern/46955: fxp(4) driver pollute logs and console with timeout messages Date: Sat, 25 Jan 2003 13:27:50 +0700 > Synopsis: fxp(4) driver pollute logs and console with timeout messages > > State-Changed-From-To: open->closed > State-Changed-By: dougb > State-Changed-When: Thu Jan 23 02:47:58 PST 2003 > State-Changed-Why: > > Your fix is the correct one. This is the expected behavior. I can understand that this might be expected behavour but I cannot agree that driver should be allowed to pollute console and make it impossile work on console. I believe fxp(4) should use log(LOG_KERN|LOG_INFO,...) instead of device_printf(...) so administrator can divert these messages and avoid erasing of terminal screen. I believe this PR should be reopened until final decision is made. Eugene Grosbein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200301250630.h0P6U2PD061445>