Comment 1 for bug 448384

Revision history for this message
Rob Oakes (robertsoakes) wrote : RE: [Bug 448384] [NEW] Scheduling does not work with crontab entry

Hi Kalle,

Thanks for the feedback. The crontab error you describe has (hopefully) been fixed. Would it be possible for you to download the most recent version (0.2.2) and give it a try from the command line? The path should now be something like /usr/local/bin/timedrive-backup. If that doesn't work, shoot me an e-mail back and we can try something else.

You can either get the files from the project's overview page here on launchpad or from
http://www.oak-tree.us/blog/index.php/science-and-technology/time-drive. The same files on softpedia (and other download sites I'm not even aware of) are usually a few versions behind.

As to accessing your backup files, there are actually two ways to do this. From your description, it sounds like you are actually using the more complicated of the two. Before clicking on the Screwdriver and Pliers (the advanced restore button), just try clicking the little green + button. This should load the archive from your saved settings without needing to specify anything. The idea behind the other button (the advanced one) is to connect to archives that aren't currently specified in your settings.

As I said before, If the new version of Time Drive doesn't solve these problems, please write back and let's see if we can figure out what's going on. Also, thanks for filing the bug. It's always good to know that people are using (and liking the program).

Cheers,

Rob

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Kalle Torstensson
Sent: Saturday, October 10, 2009 6:53 PM
To: <email address hidden>
Subject: [Bug 448384] [NEW] Scheduling does not work with crontab entry

Public bug reported:

I really like the Time Drive app, it looks to be promising everything that I have been looking for, I am backing up via ssh to a remote computer. I have a few problems though, most seriously I can't get the scheduling to work. I have tried to set it up for a daily schedule and it has added an entry to my crontab. However, it does not seem to work, seems to be a problem with the piping of the messages. My crontab entry is:
@daily nice -n 19 /usr/local/lib/python2.6/dist-packages/timedrive/timedrive-backup.py > /dev/null 2>&1

When I try to run the command from the command prompt I get the message:
Ambiguous output redirect.

Another problem that I have is that Time Drive does not remember my
backup location and user/passwd when I try to access my backup file. And
after I fill all the details it still does not work. I am not using any
encryption and I wonder if this is part of the problem? When I created
the backup I deselected the "encrypt" feature but there is no such
option for when restoring, only a blank line with "encryption key".

** Affects: time-drive
     Importance: Undecided
         Status: New

--
Scheduling does not work with crontab entry
https://bugs.launchpad.net/bugs/448384
You received this bug notification because you are a member of Time
Drive - Devel, which is subscribed to Time Drive.

Status in Time Drive: New

Bug description:
I really like the Time Drive app, it looks to be promising everything that I have been looking for, I am backing up via ssh to a remote computer. I have a few problems though, most seriously I can't get the scheduling to work. I have tried to set it up for a daily schedule and it has added an entry to my crontab. However, it does not seem to work, seems to be a problem with the piping of the messages. My crontab entry is:
@daily nice -n 19 /usr/local/lib/python2.6/dist-packages/timedrive/timedrive-backup.py > /dev/null 2>&1

When I try to run the command from the command prompt I get the message:
Ambiguous output redirect.

Another problem that I have is that Time Drive does not remember my backup location and user/passwd when I try to access my backup file. And after I fill all the details it still does not work. I am not using any encryption and I wonder if this is part of the problem? When I created the backup I deselected the "encrypt" feature but there is no such option for when restoring, only a blank line with "encryption key".