Won't Do Manual Backups

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Click the clock icon
2.
3.

What is the expected output? What do you see instead?
Backup. This message:
External Storage Location Error

The external storage location you've specified is already in use.  Please
quit any other open instances of FlyBack (or wait for their backups to
complete) before starting a new backup.

What version of the product are you using? On what operating system?
0.4.0 Xubuntu Hardy Linux

Please provide any additional information below.
I've been able to do manual backups in the past, but never timed. The time
problem may be because I want them done on Sunday, and I don't know if
Sunday is 0, 1, 6, or 7.

I've not changed the location since I was able to do the manuals. It's my
Windows partition, and is not used for anything else in Linux.

Lane

Original issue reported on code.google.com by lane.lester@gmail.com on 2 Apr 2008 at 11:53

[GoogleCodeExporter]

This is a part of the reoccurring bug with the lockfile not being deleted. If 
you
were to manually delete this lockfile (should be in your flyback directory) or 
write
a script to take care of it for you, then you should be able to run the backup 
then.
As far as the numerical representation of Sunday, I'm not entirely sure. Hope 
that helps.

Original comment by samurailink3 on 3 Apr 2008 at 2:28

[GoogleCodeExporter]

sunday followes default crontab format. look in your crontab-documentation or 
edit
the line yourself:
crontab -e

/D

Original comment by d.prisk...@gmail.com on 4 Apr 2008 at 5:36

[GoogleCodeExporter]

I've got 

@reboot rm -f /media/backup/flyback/lockfile.txt

in my crontab. Maybe this might help?

If you want to know what day Sunday is then use man 5 crontab (I think it's 0 
_and_ 7)

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

[GoogleCodeExporter]

Could be good to change the error message to include some info on the lockfile, 
just
to tell the users to delete it after a crash, for example.

Original comment by bitblit...@gmail.com on 12 Aug 2008 at 11:08

[GoogleCodeExporter]

resolved in v0.5

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

• Changed state: Fixed