Date: Thu, 27 Feb 2003 00:06:34 GMT From: Stuart Walsh <stu@ipng.org.uk> To: FreeBSD-gnats-submit@FreeBSD.org Subject: bin/48730: burncd does not handle signals and causes damage Message-ID: <200302270006.h1R06Yew000870@icecold.stu.ipng.org.uk>
next in thread | raw e-mail | index | archive | help
>Number: 48730
>Category: bin
>Synopsis: burncd does not handle signals and causes damage
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Wed Feb 26 16:10:12 PST 2003
>Closed-Date:
>Last-Modified:
>Originator: Stuart Walsh
>Release: FreeBSD 5.0-RELEASE-p1 i386
>Organization:
IPng-UK
>Environment:
System: FreeBSD icecold.stu.ipng.org.uk 5.0-RELEASE-p1 FreeBSD 5.0-RELEASE-p1 #2: Fri Feb 14 00:45:07 GMT 2003 root@icecold.stu.ipng.org.uk:/usr/obj/usr/src/sys/ICECOLD i386
Machine is an AMD XP2000+ with a LITE-ON 40x12x48 CDRW, see below for dmesg output:
acd0: CD-RW <LITE-ON LTR-40125S> at ata1-slave PIO4
>Description:
burncd does _not_ behave sanely to signals and can damage cd writers.
If one ctrl-c's burncd mid write, for whatever reason, it just exits
without either completing its task or even powering down the cd writer.
With my cd writer(I assume because of BURN-Proof) the writer stays
powered up spinning at full speed with the yellow(waiting for data)
LED illuminated. Since this incident, my cd writer has failed to write
to any CD since, even under other applications and in other environments
and has had to be replaced under warrenty.
>How-To-Repeat:
Prepare a cd for writing in the normal way and hit ctrl-c mid write.
>Fix:
Add some signal handling to shut down the writer on an exit signal!
>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?200302270006.h1R06Yew000870>