Closed GoogleCodeExporter closed 9 years ago
What I propose is that I do a check for filesize after the filesize is not
correct message is shown. A check
before ripping is nicer, but then I can't check what other applications are
adding to the disk. You might as well
be downloading some big file.
This at least stops the endless loop.
Original comment by rubyripp...@gmail.com
on 14 Aug 2009 at 3:47
Sounds good, stoping the loop is most important part. If rubyripper can catch
part of
this output
write (in buffering_write, full buffer): No space left on device
to stop riping is solution (just an idea, I'm not programmer :) )
Original comment by tolos...@gmail.com
on 17 Aug 2009 at 12:23
Fixed with commit:
http://github.com/rubyripperdev/rubyripper/commit/af3f2944a1eb00967151cf0b40f31e
355cbd
9078
Original comment by boukewou...@gmail.com
on 24 Apr 2010 at 2:24
Original issue reported on code.google.com by
tolos...@gmail.com
on 13 Aug 2009 at 9:09