Bug 30258

Summary: aborting burncd using Ctrl-C screws up CD-R/RW drive
Product: Base System Reporter: Darryl Okahata <darrylo>
Component: binAssignee: Søren Schmidt <sos>
Status: Closed FIXED    
Severity: Affects Only Me CC: darrylo
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description Darryl Okahata 2001-09-01 19:40:00 UTC 
If you hit Ctrl-C to abort burncd, burncd leaves the CD-R/RW drive in an
unusable state: the disk cannot be ejected, and any further attempt at
using burncd results in (console) messages like:

	acd0: PREVENT_ALLOW - ILLEGAL REQUEST asc=2c ascq=00 error=04
	acd0: SET_SPEED - ILLEGAL REQUEST asc=2c ascq=00 error=04
	acd0: PREVENT_ALLOW - ILLEGAL REQUEST asc=2c ascq=00 error=04

Maybe the drive isn't unlocked when Ctrl-C is hit?????

(I was burning a cd-rw, and I didn't realize that the default speed is
"1".  I wanted to abort the process, erase the cd-rw, and retry.
Hitting Ctrl-C was a bad idea.  ;-)

How-To-Repeat: 
Start a burn using burncd and hit Ctrl-C after a moment or two.
Comment 1 Mike Heffner freebsd_committer freebsd_triage 2001-12-23 07:59:52 UTC 
Responsible Changed
From-To: freebsd-bugs->sos

sos is author of burncd
Comment 2 Søren Schmidt freebsd_committer freebsd_triage 2002-01-07 19:25:07 UTC 
State Changed
From-To: open->closed

"you shouldn't do that" (tm) 

Anyhow its not possible to totally protect a userland 
program form being killed, which makes it impossible 
(well almost) to make this totally safe.