Page 1 of 1

Automate FileBot to run via Task Scheduler

Posted: 06 Feb 2020, 17:08
by davemccreath
Hi.

A complete numpty when it comes to any form of scripting!

I've managed to get FileBot Node up and running and registered. No issues apart from having to update Java. It captures files from a shared folder and moves renamed files into a media folder.

I'd like to run (Execute) FileBot through the Task Scheduler daily at 0600hrs instead of having to open FileBot Node and hit the Execute button each day.

I've tried adding FileBot as a task in 'Task Scheduler' as a scheduled task but I presume all that does is open the program, how do I get it to perform the Execute command once opened?

Many thanks in advance.

Dave

Re: Automate FileBot to run via Task Scheduler

Posted: 06 Feb 2020, 18:20
by rednoah
You can check the Task in Synology Task Scheduler. It will run the pre-configured filebot command. If you clicked Schedule, then you're already golden. By default, it's going to run at 4am, but you can configure the details in Synology Task Scheduler.

Re: Automate FileBot to run via Task Scheduler

Posted: 06 Feb 2020, 21:58
by davemccreath
Many thanks, all sorted. Happy teddy bear :)

Re: Automate FileBot to run via Task Scheduler

Posted: 11 Jul 2021, 08:22
by qytj
Hi, I have a Qnap and I am trying to figure out whether the task has been correctly scheduled, and whether I can check/change the schedules.

I got the following in my crontab, nothing seems to be a filebot task?

Code: Select all

[~] # vim /etc/config/crontab
# m h dom m dow cmd
0 3 * * * /sbin/clean_reset_pwd
0-59/15 * * * * /etc/init.d/nss2_dusg.sh
30 7 * * * /sbin/clean_upload_file
0-59/10 * * * * /etc/init.d/storage_usage.sh
30 3 * * * /sbin/notice_log_tool -v -R
35 7 * * * /sbin/qbox_util -c  > /dev/null 2>/dev/null
*/10 * * * * /sbin/config_cache_util 0
0-59/20 3 * * * /sbin/adjust_time
10 15 * * * /usr/bin/power_clean -c 2>/dev/null
17 9,21 * * * /sbin/notify_update --nc 1>/dev/null 2>&1
0 1 * * * /etc/init.d/flush_memory.sh >/dev/null 2>&1
0 4,16 * * * /sbin/hwclock -s
30 6 * * 1 /sbin/storage_util --disk_sequential_read_speed_test 1>/dev/null 2>&1
0 2 15 * * /sbin/qfstrim
0 0 1 * * /sbin/storage_util --data_scrubbing raid_id=-1 >/dev/null 2>&1
00 03 * * * sh /share/CE_CACHEDEV1_DATA/.qpkg/MalwareRemover/MalwareRemover.sh scan;#_QSC_:MalwareRemover:malware_remover_schedule:None:d::
0 23 */1 * * /sbin/qpkg_cli -U 1>/dev/null 2>/dev/null
32 2 * * * /share/CE_CACHEDEV1_DATA/.qpkg/HybridBackup/rr2/scripts/insight/insight.sh -runall >/dev/null 2>&1
0 3 * * 0 /etc/init.d/idmap.sh dump
00 03 * * * sh /share/CE_CACHEDEV1_DATA/.qpkg/MalwareRemover/Upgrade.sh;#_QSC_:MalwareRemover:malware_remover_upgrade:None:d::
0 4 * * * /sbin/auto_update 1>>/dev/null 2>>/dev/null
* * * * * /var/cache/netmgr/lock_timer.sh
0 0 * * * /usr/local/sbin/qulog-archive local_event retention 0 >/dev/null 2>&1
0 1 * * * /usr/local/sbin/qulog-archive remote_event retention 0 >/dev/null 2>&1
0 2 * * * /usr/local/sbin/qulog-archive local_access retention 0 >/dev/null 2>&1
0 3 * * * /usr/local/sbin/qulog-archive remote_access retention 0 >/dev/null 2>&1
50 7 * * * /sbin/qpkg_cli --check_license 0 > /dev/null 2>/dev/null
0 4 * * * /etc/init.d/wsd.sh restart
0 3 * * * /sbin/vs_refresh
4 3 * * 3 /etc/init.d/backup_conf.sh
0 2 * * 0 /usr/local/medialibrary/bin/mymediadbcmd checkRepairDB  >/dev/null 2>&1
0 0 * * * /usr/local/sbin/qsh nc.archive >/dev/null 2>&1
35 7 * * * /sbin/qsyncsrv_util -c  > /dev/null 2>/dev/null
30 7 * * * /sbin/version_cleaner -t 0 > /dev/null 2>/dev/null
0 0 * * * /sbin/qsyncsrv_tool --fix  > /dev/null 2>/dev/null
0 12 * * * /mnt/ext/opt/LicenseCenter/bin/qlicense_tool local_check
45 13 * * * /mnt/ext/opt/QcloudSSLCertificate/bin/ssl_agent_cli
* 4 * * * /usr/sbin/logrotate /etc/config/mc_logr.conf

Re: Automate FileBot to run via Task Scheduler

Posted: 11 Jul 2021, 11:41
by rednoah
FileBot Node does not modify your crontab. It merely prepares a command that you can then paste into some 3rd party tool or scheduler.

You can modify your system crontab with sudo vi but future QNAP updates may sometimes reset things.