Your message dated Tue, 22 Feb 2011 10:51:33 +0100
with message-id <[email protected]>
and subject line fixed
has caused the Debian Bug report #409151,
regarding dirvish should not treat files-vanished as an error
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
409151: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=409151
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dirvish
Version: 1.2-1
Severity: normal
Tags: upstream
Hi,
This is using rsync 2.6.4-6 (yes, etch is still testing so we're not using
it on that server :-)
If rsync has a "file vanished on sender" error, it apparently reports an
error code to dirvish which interprets this as "backup of this tree has
failed." But for the purpose of taking a backup, the tree has not failed -
some files disappeared, but since I still have a backup of the whole tree,
backup succeeded hence dirvish should report a success.
Why does this matter?
* monitoring
* we use hook scripts to write dirvish trees to tape for off-site backup.
I used to evaluate the dirvish success code and only write the tree to tape
if success was reported.
cheers
-- vbi
--
It was a trojan now it was identified that it was that machine the trojan
was not identified but it was identified as being that machine.
-- Jamie the spammer, 10/29/2003
pgpGFAWzyZ3dZ.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.2.1-1
confirmed. Fixed in 1.2.1. Didn't remember this bug was still open :-)
cheers
-- vbi
--
featured product: PostgreSQL - http://postgresql.org
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
