Zen of Python is being disturbed: Errors are passing silently

[GoogleCodeExporter]

What steps will reproduce the problem?
0. Have automatic backups configured
1. abend during cron'd backup leaving lockfile.txt in place
2. get busy doing other things, not noticing that cron'd flyback is
refusing to run
3. Don't check for a week or so and be amazed that you were more exposed
than you thought. ;)

What is the expected output? What do you see instead?
Flyback should alert the user by email if a backup failed because of a
lockfile.txt condition.  should be able to make flyback squeal loudly if it
knows that the backup is not working as planned.  

The Zen of Python, by Tim Peters
"Errors should never pass silently.
Unless explicitly silenced."

These conditions should cover, out of space, lockfile exists and possibly
auto delete of older backup due to user conditions.  "Hey buddy, I just
nuked backup x because you said to if this condition was true." 

The overall premise, is that flyback in cron mode needs to be able to
generate feedback for the user under warning or error conditions.

What version of the product are you using? On what operating system?
flyback 0.4 on ubuntu 7.10

Please provide any additional information below.
Should be able to send a simple email, modify config to allow 1 or more
addresses, subject, sender and mail server/port

Original issue reported on code.google.com by dunde...@gmail.com on 18 Dec 2007 at 3:21

[GoogleCodeExporter]

Or use notify-send? 

Original comment by francis....@gmail.com on 18 Jul 2008 at 3:39

[GoogleCodeExporter]

Or ... if the output goes to stderr and the crontab is set up right it will 
email you
everything anyway??

Original comment by francis....@gmail.com on 18 Jul 2008 at 3:47