Date: Fri, 19 Dec 2008 12:52:12 -0800 From: Maxim Sobolev <sobomax@FreeBSD.org> To: "David E. O'Brien" <obrien@FreeBSD.org> Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org Subject: Re: svn: head/usr.sbin/burncd Message-ID: <494C097C.1020604@FreeBSD.org> In-Reply-To: <200812192020.mBJKKEIo081792@svn.freebsd.org> References: <200812192020.mBJKKEIo081792@svn.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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: http://svn.freebsd.org/changeset/base/186337 > > 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. -Maxim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?494C097C.1020604>