Skip to content

Cannot set Shinobu's scanning interval time #718

Answered by Difegue
ResRipper asked this question in Q&A
Discussion options

You must be logged in to vote

The Background Worker doesn't normally operate on intervals but by subscribing to inotify filesystem notifications.
The initial scan might be what's consuming S3 pretty high? Otherwise it might be that AWS doesn't have proper inotify support so the worker falls back on basic polling.

In any case, I'd suggest using the provided API to stop the Shinobu worker. (There's no GUI for the stop command, since it's not something I want to actively expose to standard users)

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by Difegue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
2 participants
Converted from issue

This discussion was converted from issue #716 on December 05, 2022 23:01.