On Apr 20, 2001, Gerhard den Hollander <[EMAIL PROTECTED]> wrote:
> So it looks like amdump checks if there is enough space on the holding disk
> before it starts dumping,
Yep.
> and then simply continues dumping whitout checking if the holding disk
> becomes full, until it runs in a diskfull error and aborts the dump.
It would fall over to another holding disk, if you had one.
> The right thing (imo) would be to check every time a new chunk is written,
> and if the chunk to be written would fail the holding disk free space
> criteria, it should abort the dump.
And end up aborting the dump anyway? What's the advantage?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
