Re: mkisofs aborts but exit value is 0
Bill Davidsen <davidsen@tmr.com> wrote:
> >I would need to rethink the problem.
> >
>
> Here's a thought on that, if the read length is not the same as the
> expected length, the error is really "file size changed during read" and
> the current length can be found with stat() or similar. I'm surprised
> that this doesn't come up more often, when doing backups where files
> (such as logs) are growing, the available data size is growing, is that
> currently handled properly?
mkisofs is not a backup tool.
If you like to do backups, use apropriate tools (e.g. star).
Jörg
--
EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
js@cs.tu-berlin.de (uni)
schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
Reply to: