Resolve filelock creation problem

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Normal install /usage with crontab
   (Lockfile not deleted, or created very frequently

What is the expected output? What do you see instead?

After at most 3 or 4 backups, the lock file is made and left in the backup
directory and further automated backups are not made until it is manually
deleted.

What version of the product are you using? On what operating system?
0.4.0 on Ubuntu gutsy 2.6.22-14-generic #1 SMP

Please provide any additional information below.

 crontab didn't work, so I made my own manual entry one

30 * * * * python /media/data/python/flyback.py --backup >cronlog.txt 2>&1

I have flyback installed on a spare ext3 data partition and it also backs
up to there in my prefs, and I have it making a backup every 30 minutes. I
noticed when I added the  >cronlog.txt 2>&1 to it that not only do I get a
log in my home directory, but it also no longer creates the lockfile which
prevents future backups. At least not for me. Just thought the developer
might like to know this, I have no idea why, as I am still something of a
newb in linux. Attached is cronlog.txt.

Original issue reported on code.google.com by wvpatu...@yahoo.com on 26 Jan 2008 at 5:15

Attachments:

• cronlog.txt

[GoogleCodeExporter]

Oops, make that a backup is created every hour, on the half hour of the hour. I 
also
have it set up to back up my home directory, which is on its own partition. I 
also
have it setup to delete backups older than 7 days. I have plenty of free 
space..lol.

Attached is a screenshot of my backup directory.

Original comment by wvpatu...@yahoo.com on 26 Jan 2008 at 5:47

Attachments:

• Screenshot.png

[GoogleCodeExporter]

i'm confused to what the issue is, or if you've resolved it.  :)

Original comment by pub...@kered.org on 5 Dec 2008 at 9:18

• Changed state: NeedInfo

[GoogleCodeExporter]

resolved in v0.5

Original comment by pub...@kered.org on 27 Oct 2009 at 5:06

• Changed state: Fixed