You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, a full scan can be triggered by setting monitor_fullscan_frequency, this make the full scan be dependent on monitor_interval and the startup time of the app. In other words, a full scan may happen at undesirable times, for example, we may only want to perform a full scan at midnight when we are not using the drive or on the weekend. But a reboot or app restart will break these rules.
Describe the solution you'd like
An option in config file that support cron style schedules for triggering full scan instead of using a fixed interval.
Describe alternatives you've considered
One quick implementation is a simple scheduler that parses the options in the config and updates the start time of the next full scan over time. We can then check this computed time in monitor loop instead of the loop count.
Additional context
No response
The text was updated successfully, but these errors were encountered:
An option in config file that support cron style schedules for triggering full scan instead of using a fixed interval
Why cant you use 'cron' normally?
Use 'cron' to schedule a shell script that:
Stops your systemd service that is running --monitor
Runs the command --sync --resync --resync-auth - this has the net effect of performing your full scan
Starts your systemd service again
Essentially what you are asking for here is a way to disable 'monitor_fullscan_frequency' .. I will look at this as part of 'alpha-2' development, where setting 'monitor_fullscan_frequency; to '0' will disable it.
When this is done, you can use 'cron' to schedule what you want to occur, rather than the wheel being re-invented.
Is your feature request related to a problem? Please describe.
Currently, a full scan can be triggered by setting
monitor_fullscan_frequency
, this make the full scan be dependent onmonitor_interval
and the startup time of the app. In other words, a full scan may happen at undesirable times, for example, we may only want to perform a full scan at midnight when we are not using the drive or on the weekend. But a reboot or app restart will break these rules.Describe the solution you'd like
An option in config file that support cron style schedules for triggering full scan instead of using a fixed interval.
Describe alternatives you've considered
One quick implementation is a simple scheduler that parses the options in the config and updates the start time of the next full scan over time. We can then check this computed time in monitor loop instead of the loop count.
Additional context
No response
The text was updated successfully, but these errors were encountered: