kanth

Right, back when they introduced cache drives, it was simply /mnt/cache. Mover got introduced afterwards (shortly). Dockers could only run on the cache drive. So most of my files are simply on /mnt/cache, not on a "share" that was made for them. It's all good. I can either add a share and change all the pathing, or disable the script like I have done forever... and was previously the recommended solution. Neither is a big deal.

Again, that seems really difficult compared to just adding "disabled" to the drop down menu. I mean what is cleaner than that? Perhaps it is the way you like to think about it. For me putting in exit 0, seemed easy in the script. Yes there are ways to work around it. But asking mover.sh not to run, period, doesn't seem to me like some trying/or difficult piece of code. if [ $OPTION = disabled ]; then exit 0; *shrug*

It seems really odd to me that the scheduler allows one to schedule parity checks, or disable doing them. But doesn't allow one to _disable_ mover. I use my cache drive to hold various things on it that I _never_ want "moved" onto the unraid array. Currently the way I stop unraid from doing a mover function is to copy a script over top of the mover script that just has an exit 0 in it. It would be much better to be able to disable this functionality if the user wishes. (And simple!)