duplicity-talk
[Top][All Lists]
Advanced

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

[Duplicity-talk] Output streams


From: Yves Goergen
Subject: [Duplicity-talk] Output streams
Date: Wed, 11 May 2011 20:29:30 +0200
User-agent: Thunderbird 2.0.0.24 (Windows/20100228)

Hi,

I'm running the backup of my server automatedly with duplicity. All
output is recorded into a temp file and only if it doesn't look as
expected, an e-mail will be sent through cron. In the case of success,
no output must be generated so that cron will remain silent.

Therefore, the duplicity call redirects stdout to a file, and stderr to
&1 so that it all goes into the file. This works most of the time, but
any errors printed out by ncftpls will still be printed so far that cron
catches it and sends me an e-mail with only those ncftp error messages.
Everything else (and only that) goes into my log file.

What's wrong here? If I call

   duplicity --some-args 2>&1 >>tmpfile

then how can it be that any output from a subprocess of duplicity may
not be caught in tmpfile? I see that the process is started with

   self.popen_persist(commandline)

but I don't know Python well enough to track this one down to either
actual code or a definitive documentation of the function.

What more do I need to do to get *every* output into my log file and
*none* to stdout?

OS: Ubuntu 10.4
duplicity version 0.6.08b

-- 
Yves Goergen "LonelyPixel" <address@hidden>
Visit my web laboratory at http://beta.unclassified.de



reply via email to

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