bugrdiff-backup - Bugs: bug #9636, UpdateError, although ignorable,...

 
 

bug #9636: UpdateError, although ignorable, makes rdiff-backup return a non-0 return code

Submitter:  None
Submitted:  Tue 13 Jul 2004 10:19:02 PM UTC
   
 
Category:  None Severity:  3 - Normal
Item Group:  None Status:  Works For Me
Privacy:  Public Assigned to:  None
Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Mon 08 Aug 2005 04:02:09 AM UTC, comment #5: 

Closing because no new comments - reopen if it still doesn't work.

Benedict Escoto <bescoto>
Group administrator
Sun 24 Apr 2005 04:34:00 PM UTC, comment #4: 

I think I was unclear also in my response (and there was a typo).  The way it is supposed to work (and the way it looks like it works) is that rdiff-backup will return a zero value unless it exits abnormally.  So if you get an UpdateError and the backup still completes, it will still exit with value 0.

However, if it exits with a fatal (non-recoverable) error, it will exit with non-zero value.  So if you saw rdiff-backup exiting this way, perhaps there was both an UpdateError and a fatal error.  It may have looked like the update error was the cause, but really it was the fatal error.

So perhaps it already works the way you want it to?

Benedict Escoto <bescoto>
Group administrator
Fri 22 Apr 2005 10:35:56 PM UTC, comment #3: 

I tried to point out that it was inconvenient for me that rdiff-backup returns a non-zero value even for a trivial UpdateError which is hardly avoidable.

Some log-files for example will almost always fail simply because there's no practical way to make them stop growing while running rdiff-backup.

That's why I was trying to get you interested in a fictional '--ignore-update-error' flag.

I hope I've made myself sufficiently clear now.

Oh, and sorry for my late response. We both seem to be slow responders ;-)

Rowan Rodrik van der Molen <bigsmoke>
Sat 26 Mar 2005 08:34:52 PM UTC, comment #2: 

Sorry for the delay answering this.  Are you sure about this?  Perhaps there was an UpdateError, but then rdiff-backup failed for some other reason, and that's why the return value was 0.

Benedict Escoto <bescoto>
Group administrator
Tue 13 Jul 2004 10:24:26 PM UTC, comment #1: 

I submitted the request before registering. This is to let you know who submitted this...

Rowan Rodrik van der Molen <bigsmoke>
Tue 13 Jul 2004 10:19:02 PM UTC, original submission:  

When using rdiff-backup in automatic backup scripts, it can be very inconvenient that it returns an error code whenever an UpdateError is encountered. If changing the behaviour doesn't suit the devs, maybe you could add an option '--ignore-update-error' which makes it return a 0 regardless of update errors.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.

 

Follow 3 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2005-08-08 bescoto StatusNone Works For Me
    Open/ClosedOpen Closed
2004-07-13 bigsmoke Carbon-Copy- Added bigsmoke

Back to the top

Powered by Savane 3.13-caa5.
Corresponding source code