Hi Wolfgang,
On 03-Feb-99 Wolfgang Weisselberg wrote:
> Hi!
>
> Trying to kill the keyboard, [EMAIL PROTECTED] produced:
>> You might be aware of this, but if any files are growing or
>> changing their status in any way either during or between backups
>> or verifications, BRU or any other backup utility will show errors.
>> BRU is fairly smart about this in that it returns an error 1 for
>> warnings and an error 2 for hard errors, afio returns error 1 for
>> everything which is problematic.
>
> True enough, but afio will spit out the changed files (and some,
> e.g. logfiles, *will* change), so you can capture the output and
> check it with your eyes --- or a script --- for files that are
> 'allowed' to change.
Yup, my script does that--it sends the root user e-mail which I
print out and keep for two weeks. Usually only /var/log/messages
and one of my backup log files are to blame and only on the root
filesystem.
> Alternatively, you could boot to a different system (bootdisk,
> second system on your HD) and backup from there. Of course
> that kills uptime, running daemons, ... You could also use the
> /linuxrc mechanism with an initial ramdisk, so you could continue
> booting into your system after backup is finished.
I could do this, but 7/24 systems can't.
Carl
----------------------------------
E-Mail: Carl J. Nobile <[EMAIL PROTECTED]>
Date: 03-Feb-99
Time: 17:43:01
----------------------------------
