svn: head/usr.sbin/burncd

Maxim Sobolev sobomax at
Fri Dec 19 21:20:19 UTC 2008

Should not it be better to implement this on the kernel side when the 
device is closed abruptly?

David E. O'Brien wrote:
> Author: obrien
> Date: Fri Dec 19 20:20:14 2008
> New Revision: 186337
> URL:
> Log:
>   burncd(8) doesn't handle signals and interrupting burncd during operation.
>   For example, ^C (SIGINT) may leave the drive spinning and locked.
>   This may also happen if you try to write a too-large image to a disc
>   and burncd(8) exits with an I/O error.
>   Add signal handling by doing a CDRIOCFLUSH ioctl to attempt to leave
>   burner in a sane state when burning is interrupted with SIGHUP, SIGINT,
>   SIGTERM, or in case an I/O error occurs during write.
>   Note, that blanking will still continue after interrupt but it seems to
>   finish correctly even after burncd(8) has quit.


More information about the svn-src-all mailing list