Comment 3 for bug 316500

I'm developer of cdrskin and quite late with this comment, i fear.
But for the records:

Without seeing the original error message of cdrskin, i can only
guess that the problem is some O_EXCL usage of the drive
(by some automat).
One can keep cdrskin from respecting such Linux specific locks
by its option --drive_not_exclusive .

For finding the culprit of the suspected open(O_EXCL), one
should try a command like:

  lsof | fgrep /dev/sr0

--------------------------------------------------------------------------------

To those who take care for the support here:

Be invited to notify me about any report where cdrskin, xorriso
or the underlying libraries are mentioned with problems.
E.g. via: <email address hidden>