[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Rdiff-backup-bugs] [bug #17980] Feature request: better handling of gro

From: Per Cederqvist
Subject: [Rdiff-backup-bugs] [bug #17980] Feature request: better handling of growing log files
Date: Thu, 12 Oct 2006 11:26:40 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20060915 CentOS/ Firefox/ pango-text


                 Summary: Feature request: better handling of growing log
                 Project: rdiff-backup
            Submitted by: ceder
            Submitted on: Thursday 10/12/2006 at 13:26
                Category: None
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open



I'm using rdiff-backup to back up a system that almost always writes to
/var/log/messages while the backup is running.  So my backup of that file is
old and stale.

I have a suggestion: when starting to back up a file, check how large it is. 
While doing the actual backup, only handle the initial part that existed at
the start of the operation.  If the file changes while the backup is running,
check if the only change is that new data has been appended.  If so, don't
fail with an UpdateError.  Log a warning, and make sure that the initial part
of the log file is properly backed up.

Even better: make the warning configurable on a per-file basis.  You could
have options --logfile, --logfile-filelist, --logfile-globbing-filelist et c
to let the user define which files that are log files (with the same syntax
as the --exclude options).  Only produce the warning for file that are not
configured to be log files.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]