I had some difficulties scheduling a job on Linux Ubuntu. I used the instructions below, but the job just didn't wanted to start automatically until I found out that one needs to make the FFS-batch file executable. IMO for Linux beginners it would help if that would be mentioned briefly in the FFS-manual.
Ubuntu Linux Gnome-schedule:
Install Gnome-schedule if necessary: sudo apt-get install gnome-schedule
Go to System → Preferences → Scheduled tasks
Enter the command: <FreeFileSync installation folder>/FreeFileSync <job name>.ffs_batch
Linux Gnome-Schedule - FFS batchfile needs to be executable
- Posts: 11
- Joined: 11 Apr 2006
- Site Admin
- Posts: 7211
- Joined: 9 Dec 2007
This doesn't make any sense, are you sure you didn't mean setting the executable bit for the "FreeFileSync" binary?
- Posts: 11
- Joined: 11 Apr 2006
sorry for the late reply.
I don't know what went wrong, but you're right - it doesn't make sense and it was not causing my problems.
I know found the real problem. In the current version (2.1.1) of Gnome-Schedule one can not only select "no output", but also x-window. For me the "no output" option doesn't work (it is just not starting). When I select "X-Windows" , then it works fine.
When saving a FFS-batch file, one can also specify that FFS should be executed minimized. I assume that this is the same function as "no output" and this should probably be used instead of "no output".
If you can reproduce what I'm talking about, the FFS manual for Gnome-Schedule should probably be updated.
Thanks.
I don't know what went wrong, but you're right - it doesn't make sense and it was not causing my problems.
I know found the real problem. In the current version (2.1.1) of Gnome-Schedule one can not only select "no output", but also x-window. For me the "no output" option doesn't work (it is just not starting). When I select "X-Windows" , then it works fine.
When saving a FFS-batch file, one can also specify that FFS should be executed minimized. I assume that this is the same function as "no output" and this should probably be used instead of "no output".
If you can reproduce what I'm talking about, the FFS manual for Gnome-Schedule should probably be updated.
Thanks.
- Site Admin
- Posts: 7211
- Joined: 9 Dec 2007
I don't know what "No output" means in Gnome schedule: If it means "no GUI", then this is a problem because FreeFileSync always requires a GUI, even if FreeFileSync runs minimized!
Maybe this is the problem with "no output" and FreeFileSync not starting?
Anyway, it doesn't matter: I just tested Gnome scheduler with default settings and scheduling FreeFileSync works fine. The standard value for output is labeled "Default behavior". I've updated the help file with a new screenshot of the current Gnome scheduler suggesting to leave everything at their default values.
Maybe this is the problem with "no output" and FreeFileSync not starting?
Anyway, it doesn't matter: I just tested Gnome scheduler with default settings and scheduling FreeFileSync works fine. The standard value for output is labeled "Default behavior". I've updated the help file with a new screenshot of the current Gnome scheduler suggesting to leave everything at their default values.
- Posts: 11
- Joined: 11 Apr 2006
yes, I guess "no output" means suppressing the FFS window, but I don't know for sure either.