Hello,
I am talking this issue to LKML now.
Short story: using O_EXCL on /dev/srX alone does not help to prevent
other process from killing your burn process by just reading the
/dev/sgX device associated with yours, and vice versa. We have done the
best we could to make safe operation (in contrary to Schilling's
kill-this-evil-hald-thing bitching) but that is not enough, the locking
has to be established on kernel layer.
Long story:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413960https://bugzilla.novell.com/show_bug.cgi?id=226019http://lists.alioth.debian.org/pipermail/debburn-devel/2007-February/000297.html
and other error messages.
There is AFAICS no simple way to establish locking across the driver
borders. If kernel developers have a good idea, any help is appreciated.
Below are the typical symptoms: wodim operates via /dev/sgX because the
user chosen it this way, some other process (most likely hald) comes
along and reads from /dev/sr0 and the drive gets confused. Boom.
Regards,
Eduard.
* Gerald Lutter [Mon, Mar 26 2007, 06:10:44PM]:
^^^^^^^^^
...
Track 01: 0 of 692 MB written.
...
--
* Amaya knuddelt Ganneff because of his email to private :*
<Ganneff> ich wusst doch dass die irgendwo was schlechtes nach sich zieht.
-