Date: Wed, 26 Dec 2001 08:53:33 -0800 (PST) From: Chris Dillon <cdillon@wolves.k12.mo.us> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/33202: sys/dev/mly/mly.c minor mly_printf cosmetic problem Message-ID: <200112261653.fBQGrXL57068@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 33202 >Category: kern >Synopsis: sys/dev/mly/mly.c minor mly_printf cosmetic problem >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Dec 26 09:00:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Chris Dillon >Release: 4.4-STABLE >Organization: >Environment: FreeBSD duey.wolves.k12.mo.us 4.4-STABLE FreeBSD 4.4-STABLE #21: Wed Dec 19 17:30:05 CST 2001 cdillon@duey.wolves.k12.mo.us:/usr/obj/usr/src/sys/DUEY i386 >Description: In mly_process_event of sys/dev/mly/mly.c, the mly_printf for event class 'e' (enclosure) does not appear to output a terminating newline like the rest of the event classes. This results in logfile output such as this: Dec 26 05:44:32 duey /kernel: mly0: enclosure 1 temperature sensor 0 failedmly0: enclosure 1 temperature sensor 0 failedmly0: enclosure 1 temperature sensor 0 failed >How-To-Repeat: Cause an enclosure event, or be unlucky enough to witness one. >Fix: Since I won't be able to test any changes I make (I don't know how to cause an enclosure event out of the blue, and the box in question is also not in front of me right now) and since I'm really not all that good with C anyway, I'll leave this up to someone more qualified. >Release-Note: >Audit-Trail: >Unformatted: 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?200112261653.fBQGrXL57068>