Installing
Available from the official add-on repository
FAQ
XBMC continuously cleans/scans
This probably mean you have an app running that continuously reads and/or deletes files in the media source. Normally downloading applications and such should not cause this (file modifications are ignored) but certain ones dumps a lot of temporary files to the disk.
Other issues
1. Enable debug logging
2. Restart XBMC
3. Produce the error
4. Post the complete debug log in this thread and I will try to help.
Using watchdog with network shares
Frodo:
Now works out-of-the-box
Eden:
1. Manually mount the network share to a local directory.
2. Add this directory as a media source in XBMC. (You may choose to exclude this folder from directory updates. If you do not, you should remove the old media source if you had one.)
3. Goto Settings > Add-ons > Enabled add-ons > XBMC.org Add-ons > Services > Library watchdog > Configure. Set 'Method' to 'Polling'.
4. Restart XBMC.
Eden + MySQL
Follow the same procedure as above on all system. The important step is to enable "Exclude path from library updates" when you setup the locally mounted folder.
Implementation details
Window Vista and newer, Linux, OS X, BSD will use event based system calls, Windows XP, others platforms and mounted network shares will use polling.
Source code on github: http://github.com/takoi/xbmc-addon-watchdog
What is the difference between "polling" and "syscall"
Polling involves continuously checking new files, while syscall register a callback. Basically, polling will use more cpu, but usually it shouldn't be noticeable.
If using polling, will it hog the disks and prevent them from spinning down
No. When there's nothing being written to the drives, the OS will usually cache the entire directory structure. If for some reason disk activity persist, you might want to look into increasing the cache space in you OS.
Polling methods:
If you are experiencing performance issues you can select another method for network shares. Here's an explanation of the different polling methods you can choose:
Depth 1: very fast. independent of number of files
Code:
./media source/
folder a/ <-- detected (will always scan and clean (if enabled). unknown if it was added or removed)
folder b/ <-- not detectedDepth 2: performance depends on number of directories and files in top folder (media source) only
Code:
./media source/
folder a/ <-- detected as new
folder b/ <-- detected (will always scan and clean (if enabled). unknown if it was added or removed)
folder c/ <-- not detectedDepth inf.: performance depends on total number of directories and files. Will detect everything, also whether a file was added or removed.
Search
Help