Re: Getting paranoia to quit on CD eject
Bill Davidsen <[email protected]> Sun, 17 Oct 2004 08:03:13 -0400
| Newsgroups | gmane.comp.audio.cd-paranoia.general |
|---|---|
| Organization | TMR Associates Inc, Schenectady NY |
| Message-ID | <[email protected]> |
Ben Williams wrote: > Peter Jones wrote: > >> On Wed, 2004-10-13 at 12:37 -0400, Ben Williams wrote: >> >> >>> Monty wrote: >>> >>> >>> >>>> Actually, some people purposely pull the trick of ejecting the disk >>>> during a rip and putting it back in as a way of resetting some drives >>>> that get stuck. Locking the door breaks that behavior, as does >>>> aborting on a 'NOT READY' SCSI sense code :-) >>>> >>>> >>> >>> Would this be tough to do a patch for? My problem is that the device >>> I'm working on has no user interface, so the only way for the user to >>> abort ripping is to eject the CD. Aborting on a 'NOT READY' SCSI >>> sense code is exactly what I want. >>> >> >> >> Well, making it abort would be simple, but Monty has a pretty good point >> here. It would make sense to have this as a config option... >> >> > Can anyone point me in the right direction in making this patch? I > looked through the paranoia code a little bit but couldn'r really find > what I was looking for. I'm not worried about getting this accepted into > paranoia, I just need it for my personal use. Why not just kill the process? On that topic, it would be nice if there were more control over error handling, such as a limit on errors per track, after which the track would be abandoned, etc. -- bill davidsen <[email protected]> CTO TMR Associates, Inc Doing interesting things with small computers since 1979