It's been a while since this bug saw some activity, but I'd like to try my luck
anyway.
Tristan - how did you detect readom's silent failure? I'm trying to do
something similar from a bash script
(bump...)
--
Silent failure when out of /tmp space
https://bugs.launchpad.net/bugs/178774
You recei
It has been a while, but I do recall how it works. gnomebaker calls
other tools, in this case readom, and checks the return codes from these
tools. The problem is this part of my previous post:
$ readom dev=/dev/sr0 f=/tmp/tmpfs/test.iso
...
readom: No space left on device. Cannot write '/tmp/tmpf
thanks for the fast reply. I apologize, I wasn't very clear in my question.
I'm calling readom from a different, custom script (not using gnomebaker).
In more detail, I'm instructing readom to create a cd/dvd image from optical
media I place in the drive. Problem is, that if readom encounters bad
I'm afraid you're stuck with grepping for errors without modifying the
readom source. I worked around the bug by supplying a sufficient temp
directory for gnomebaker to make the error I encountered unlikely.
A correct fix here is to fix readom to return with an error exit code
when it detects erro
readom is a very old version from the program readcd.
readcd is a descendent from a 23 year old demo/skeleton program that originally
was
written to demonstrate the first SCSI pass through driver. Although readcd
itself does a lot
of error checking and recovery, it was never tested for having a
Just a small additional comment. The original unmodified readcd program (even
in
case it is very old) definitely does not exit(0) in your case but rather
returns:
Condition not caught: file_write_err.
Abort - core dumped
exit code is 6 in this case.
The new readcd exits this way:
addr: 100
** Changed in: cdrkit (Ubuntu)
Sourcepackagename: gnomebaker => cdrkit
Importance: Undecided => Low
--
Silent failure when out of /tmp space
https://bugs.launchpad.net/bugs/178774
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
Would you be willing to provide a patch for this?
--
Silent failure when out of /tmp space
https://bugs.launchpad.net/bugs/178774
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
I decided to take a deeper look into it, and it looks like it's not
gnomebaker's fault; it's cdrkit's fault. Should this bug be filed
elsewhere?
`readom` will detect the error, but it returns a success error code. I
wrote a quick sh script wrapper to return a failed exit code. gnomebaker
picks it
** Changed in: cdrkit (Ubuntu)
Sourcepackagename: gnomebaker => cdrkit
Importance: Undecided => Low
--
Silent failure when out of /tmp space
https://bugs.launchpad.net/bugs/178774
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
It's been a while since this bug saw some activity, but I'd like to try my luck
anyway.
Tristan - how did you detect readom's silent failure? I'm trying to do
something similar from a bash script
(bump...)
--
Silent failure when out of /tmp space
https://bugs.launchpad.net/bugs/178774
You recei
It has been a while, but I do recall how it works. gnomebaker calls
other tools, in this case readom, and checks the return codes from these
tools. The problem is this part of my previous post:
$ readom dev=/dev/sr0 f=/tmp/tmpfs/test.iso
...
readom: No space left on device. Cannot write '/tmp/tmpf
thanks for the fast reply. I apologize, I wasn't very clear in my question.
I'm calling readom from a different, custom script (not using gnomebaker).
In more detail, I'm instructing readom to create a cd/dvd image from optical
media I place in the drive. Problem is, that if readom encounters bad
I'm afraid you're stuck with grepping for errors without modifying the
readom source. I worked around the bug by supplying a sufficient temp
directory for gnomebaker to make the error I encountered unlikely.
A correct fix here is to fix readom to return with an error exit code
when it detects erro
readom is a very old version from the program readcd.
readcd is a descendent from a 23 year old demo/skeleton program that originally
was
written to demonstrate the first SCSI pass through driver. Although readcd
itself does a lot
of error checking and recovery, it was never tested for having a
Just a small additional comment. The original unmodified readcd program (even
in
case it is very old) definitely does not exit(0) in your case but rather
returns:
Condition not caught: file_write_err.
Abort - core dumped
exit code is 6 in this case.
The new readcd exits this way:
addr: 100
It's been a while since this bug saw some activity, but I'd like to try my luck
anyway.
Tristan - how did you detect readom's silent failure? I'm trying to do
something similar from a bash script
(bump...)
--
Silent failure when out of /tmp space
https://bugs.launchpad.net/bugs/178774
You recei
It has been a while, but I do recall how it works. gnomebaker calls
other tools, in this case readom, and checks the return codes from these
tools. The problem is this part of my previous post:
$ readom dev=/dev/sr0 f=/tmp/tmpfs/test.iso
...
readom: No space left on device. Cannot write '/tmp/tmpf
thanks for the fast reply. I apologize, I wasn't very clear in my question.
I'm calling readom from a different, custom script (not using gnomebaker).
In more detail, I'm instructing readom to create a cd/dvd image from optical
media I place in the drive. Problem is, that if readom encounters bad
I'm afraid you're stuck with grepping for errors without modifying the
readom source. I worked around the bug by supplying a sufficient temp
directory for gnomebaker to make the error I encountered unlikely.
A correct fix here is to fix readom to return with an error exit code
when it detects erro
readom is a very old version from the program readcd.
readcd is a descendent from a 23 year old demo/skeleton program that originally
was
written to demonstrate the first SCSI pass through driver. Although readcd
itself does a lot
of error checking and recovery, it was never tested for having a
Just a small additional comment. The original unmodified readcd program (even
in
case it is very old) definitely does not exit(0) in your case but rather
returns:
Condition not caught: file_write_err.
Abort - core dumped
exit code is 6 in this case.
The new readcd exits this way:
addr: 100
Would you be willing to provide a patch for this?
--
Silent failure when out of /tmp space
https://bugs.launchpad.net/bugs/178774
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
I decided to take a deeper look into it, and it looks like it's not
gnomebaker's fault; it's cdrkit's fault. Should this bug be filed
elsewhere?
`readom` will detect the error, but it returns a success error code. I
wrote a quick sh script wrapper to return a failed exit code. gnomebaker
picks it
Would you be willing to provide a patch for this?
--
Silent failure when out of /tmp space
https://bugs.launchpad.net/bugs/178774
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
I decided to take a deeper look into it, and it looks like it's not
gnomebaker's fault; it's cdrkit's fault. Should this bug be filed
elsewhere?
`readom` will detect the error, but it returns a success error code. I
wrote a quick sh script wrapper to return a failed exit code. gnomebaker
picks it
** Changed in: cdrkit (Ubuntu)
Sourcepackagename: gnomebaker => cdrkit
Importance: Undecided => Low
--
Silent failure when out of /tmp space
https://bugs.launchpad.net/bugs/178774
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
Would you be willing to provide a patch for this?
--
Silent failure when out of /tmp space
https://bugs.launchpad.net/bugs/178774
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
I decided to take a deeper look into it, and it looks like it's not
gnomebaker's fault; it's cdrkit's fault. Should this bug be filed
elsewhere?
`readom` will detect the error, but it returns a success error code. I
wrote a quick sh script wrapper to return a failed exit code. gnomebaker
picks it
** Changed in: cdrkit (Ubuntu)
Sourcepackagename: gnomebaker => cdrkit
Importance: Undecided => Low
--
Silent failure when out of /tmp space
https://bugs.launchpad.net/bugs/178774
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
It's been a while since this bug saw some activity, but I'd like to try my luck
anyway.
Tristan - how did you detect readom's silent failure? I'm trying to do
something similar from a bash script
(bump...)
--
Silent failure when out of /tmp space
https://bugs.launchpad.net/bugs/178774
You recei
It has been a while, but I do recall how it works. gnomebaker calls
other tools, in this case readom, and checks the return codes from these
tools. The problem is this part of my previous post:
$ readom dev=/dev/sr0 f=/tmp/tmpfs/test.iso
...
readom: No space left on device. Cannot write '/tmp/tmpf
thanks for the fast reply. I apologize, I wasn't very clear in my question.
I'm calling readom from a different, custom script (not using gnomebaker).
In more detail, I'm instructing readom to create a cd/dvd image from optical
media I place in the drive. Problem is, that if readom encounters bad
I'm afraid you're stuck with grepping for errors without modifying the
readom source. I worked around the bug by supplying a sufficient temp
directory for gnomebaker to make the error I encountered unlikely.
A correct fix here is to fix readom to return with an error exit code
when it detects erro
readom is a very old version from the program readcd.
readcd is a descendent from a 23 year old demo/skeleton program that originally
was
written to demonstrate the first SCSI pass through driver. Although readcd
itself does a lot
of error checking and recovery, it was never tested for having a
Just a small additional comment. The original unmodified readcd program (even
in
case it is very old) definitely does not exit(0) in your case but rather
returns:
Condition not caught: file_write_err.
Abort - core dumped
exit code is 6 in this case.
The new readcd exits this way:
addr: 100
It's been a while since this bug saw some activity, but I'd like to try my luck
anyway.
Tristan - how did you detect readom's silent failure? I'm trying to do
something similar from a bash script
(bump...)
--
Silent failure when out of /tmp space
https://bugs.launchpad.net/bugs/178774
You recei
It has been a while, but I do recall how it works. gnomebaker calls
other tools, in this case readom, and checks the return codes from these
tools. The problem is this part of my previous post:
$ readom dev=/dev/sr0 f=/tmp/tmpfs/test.iso
...
readom: No space left on device. Cannot write '/tmp/tmpf
thanks for the fast reply. I apologize, I wasn't very clear in my question.
I'm calling readom from a different, custom script (not using gnomebaker).
In more detail, I'm instructing readom to create a cd/dvd image from optical
media I place in the drive. Problem is, that if readom encounters bad
I'm afraid you're stuck with grepping for errors without modifying the
readom source. I worked around the bug by supplying a sufficient temp
directory for gnomebaker to make the error I encountered unlikely.
A correct fix here is to fix readom to return with an error exit code
when it detects erro
readom is a very old version from the program readcd.
readcd is a descendent from a 23 year old demo/skeleton program that originally
was
written to demonstrate the first SCSI pass through driver. Although readcd
itself does a lot
of error checking and recovery, it was never tested for having a
Just a small additional comment. The original unmodified readcd program (even
in
case it is very old) definitely does not exit(0) in your case but rather
returns:
Condition not caught: file_write_err.
Abort - core dumped
exit code is 6 in this case.
The new readcd exits this way:
addr: 100
Would you be willing to provide a patch for this?
--
Silent failure when out of /tmp space
https://bugs.launchpad.net/bugs/178774
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
I decided to take a deeper look into it, and it looks like it's not
gnomebaker's fault; it's cdrkit's fault. Should this bug be filed
elsewhere?
`readom` will detect the error, but it returns a success error code. I
wrote a quick sh script wrapper to return a failed exit code. gnomebaker
picks it
** Changed in: cdrkit (Ubuntu)
Sourcepackagename: gnomebaker => cdrkit
Importance: Undecided => Low
--
Silent failure when out of /tmp space
https://bugs.launchpad.net/bugs/178774
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
Would you be willing to provide a patch for this?
--
Silent failure when out of /tmp space
https://bugs.launchpad.net/bugs/178774
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
I decided to take a deeper look into it, and it looks like it's not
gnomebaker's fault; it's cdrkit's fault. Should this bug be filed
elsewhere?
`readom` will detect the error, but it returns a success error code. I
wrote a quick sh script wrapper to return a failed exit code. gnomebaker
picks it
It's been a while since this bug saw some activity, but I'd like to try my luck
anyway.
Tristan - how did you detect readom's silent failure? I'm trying to do
something similar from a bash script
(bump...)
--
Silent failure when out of /tmp space
https://bugs.launchpad.net/bugs/178774
You recei
It has been a while, but I do recall how it works. gnomebaker calls
other tools, in this case readom, and checks the return codes from these
tools. The problem is this part of my previous post:
$ readom dev=/dev/sr0 f=/tmp/tmpfs/test.iso
...
readom: No space left on device. Cannot write '/tmp/tmpf
thanks for the fast reply. I apologize, I wasn't very clear in my question.
I'm calling readom from a different, custom script (not using gnomebaker).
In more detail, I'm instructing readom to create a cd/dvd image from optical
media I place in the drive. Problem is, that if readom encounters bad
I'm afraid you're stuck with grepping for errors without modifying the
readom source. I worked around the bug by supplying a sufficient temp
directory for gnomebaker to make the error I encountered unlikely.
A correct fix here is to fix readom to return with an error exit code
when it detects erro
readom is a very old version from the program readcd.
readcd is a descendent from a 23 year old demo/skeleton program that originally
was
written to demonstrate the first SCSI pass through driver. Although readcd
itself does a lot
of error checking and recovery, it was never tested for having a
Just a small additional comment. The original unmodified readcd program (even
in
case it is very old) definitely does not exit(0) in your case but rather
returns:
Condition not caught: file_write_err.
Abort - core dumped
exit code is 6 in this case.
The new readcd exits this way:
addr: 100
** Changed in: cdrkit (Ubuntu)
Sourcepackagename: gnomebaker => cdrkit
Importance: Undecided => Low
--
Silent failure when out of /tmp space
https://bugs.launchpad.net/bugs/178774
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
54 matches
Mail list logo