duplicity-team team mailing list archive
-
duplicity-team team
-
Mailing list archive
-
Message #03662
Re: [Question #295948]: Failed backups: /etc/.pwd.lock
Question #295948 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/295948
Aaron Whitehouse requested more information:
Vlatko/DiagonalArg,
Can one of you please run the command directly in duplicity (DiagonalArg
found his command using `ps ux | grep duplicity`) and copy and paste the
results here?
I am trying to figure out if duplicity is failing or if duplicity has
just changed its output slightly and that is causing (only) deja dup to
fail.
This is a bit of a tough one. Technically you have asked duplicity to
back up all of /etc/ with no exceptions and duplicity couldn't do that
because some of the files could not be read. From duplicity's
perspective, it did really fail and the proper way to deal with this at
the command line is to just an exception not to back up the files that
you don't have access to read.
Historically, however, I believe that this warned on each locked file
and gave an error count that said how many files could not be read, but
actually exited without error. I didn't intend to change that behaviour
with the relevant commit here, to avoid these kinds of problems, so my
plan is to make it work the same way that it did before (if I have in
fact changed it somehow).
--
You received this question notification because your team duplicity-team
is an answer contact for Duplicity.