Closed GoogleCodeExporter closed 9 years ago
was it at one point there?
enter the prefs and resave. it will update the crontab with the program's new
location.
see the following line for how i get where you're running from:
RUN_FROM_DIR = os.path.abspath(os.path.dirname(sys.argv[0])) + '/'
Original comment by pub...@kered.org
on 11 Dec 2007 at 10:04
I tried that but it did not work. I manually fixed it for myself.
Original comment by Danyhadd...@gmail.com
on 13 Jan 2008 at 11:25
[deleted comment]
i tried too, but it doesn't work...
how did you fix it?
Original comment by sottosup...@gmail.com
on 10 Feb 2008 at 7:47
I had the same problem with scheduled backups not functioning.
I am running PCLinuxOS 2007 and flyback-0.4. Since I manually installed it, my
flyback.py executable installed at /usr/local/bin/flyback/flyback.py
I am setting it up to run as root, so the cron entry is stored at
/var/spool/cron/root. What I noticed was that the path to the flyback.py
script in
the cron entry was getting set to whatever directory I happened to be in when I
started the flyback.py script.
For instance, when I was in root's home directory and started flyback with the
command:
/usr/local/bin/flyback/flyback.py
and set a schedule in the preferences dialog, my /var/spool/cron/root entry
read:
46 8 * * * python /root/flyback.py --backup #flyback
Obviously, this will not work because that is not where flyback.py is.
I know very little about python, but near as I can tell the offending line is
line
#598 in flyback.py which reads:
existing_crons.append(c + ' python '+ os.getcwd() +'/flyback.py --backup
#flyback\n')
After changing this line to read:
existing_crons.append(c + ' python '+ RUN_FROM_DIR +'flyback.py --backup
#flyback\n')
everything seems to work OK. Like I say, I'm no python expert, so I don't know
if
this will break something else, but it does not seem to create any problems,
and my
cron entry is now correct.
Original comment by hankc...@gmail.com
on 3 Mar 2008 at 2:08
Modification made by hankcurt (comment # 5) fixes the issue with the crontab.
The weird part is that it is still not fixed on ver 0.5.0 on svn.
I think this project may have been abandoned. Anyone knows?
Original comment by alejandr...@gmail.com
on 8 Sep 2008 at 7:40
i think this is fixed in the partial rewrite for 0.6.x. re-open if i'm wrong.
Original comment by pub...@kered.org
on 19 Feb 2010 at 4:52
Original issue reported on code.google.com by
Danyhadd...@gmail.com
on 11 Dec 2007 at 4:01