Alexandre Oliva wrote:
> On Jan 4, 2001, "John R. Jackson" <[EMAIL PROTECTED]> wrote:
>
> >> OK. That means you have a "process in the middle" that saves stdin to
> >> a file and only starts outputting to stdout once it gets a signal.
>
> > We cannot assume we have file space on the client. I suspect it would
> > be easier to just load up the blocks in memory, but that then implies
> > a potential for a lot of memory use.
>
> Besides, we'd have to start the backups in update mode. What if
> there's so little data in the disk that it ends up updating
> /etc/dumpdates before we get a chance to stop it?
DANGEROUS! Forgot I suggested anything... ;-)
Patch recieved and applied, and I'll keep an eye on the backup
tonight. Yesterday ran fine without the patch, and without me
"supervising". It doesn't go wrong all the time. So we'll have to
wait a few days to see if it really helps.
Another suggestion: This is open source. How about asking the guys
doing "dump" if they can implement a "estimate, then exit" mode. The
current method would then only be used for dump programs that don't
have that extension.
Roger.
--
** [EMAIL PROTECTED] ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots.
* There are also old, bald pilots.
