Question #109951 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/109951
mogliii posted a new comment:
May I suggest one more
If you use
duplicity src tgt 21 | tee logfile
you will get both errors and normal stdout in the logfile PLUS you see
everything on the screen.
Question #109951 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/109951
mogliii posted a new comment:
One more correction: use
duplicity src tgt 21 | tee -a logfile
to not overwrite the previous logfile
--
You received this question notification because you are a
New question #109951 on Duplicity:
https://answers.launchpad.net/duplicity/+question/109951
I'm running duplicity from a script (triggered by a cronjob) and piping the
output to a log file:
duplicity my_options source target logfile
BTW I'm using -v5 as logging verbosity.
When duplicity
Question #109951 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/109951
Status: Open = Answered
edso proposed the following answer:
duplicity is logging errors to STDERR .. hence using
#duplicity my_options source target logfile 21
will do what you want.
learn more
Question #109951 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/109951
Status: Answered = Solved
Rodrigo Alvarez confirmed that the question is solved:
Thank you both!
I only tried
duplicity options src tgt logfile 21
And it seems to work like a charm : )
--
5 matches
Mail list logo
