I'm trying to add in this line to the config/go script from a thread here

 

- http://lime-technology.com/forum/index.php?topic=10027.msg95446#msg95446

 

So to disable the mover, it says I need to add in the line

 

"mv /usr/local/sbin/mover /usr/local/sbin/mover.old"

 

Into that config/go script. I just don't know where this script is or how to access it

 

Is this still the accepted way to disable the mover or should I do it a different way?

Why not just set your shares to not use the cache drive?

 

The "go" file is stored on your flash drive in the config folder

Why not just set your shares to not use the cache drive?

 

The "go" file is stored on your flash drive in the config folder

 

I do have my user shares to not use the cache drive. However, I run apps like sabnzbd and would like to have them extract what I download onto the cache drive. So I want to disable the mover so there aren't any conflicts when something is being extracted, downloaded, etc

 

Which actually, now that I think about it. I set the 'appdata' folder to cache only. Which the mover is said to not touch that folder. Could I create a custom folder, say 'downloads' in that appdata folder within the cache disk and then have stuff downloaded there to be protected by the mover? Or will the mover only refuse to touch the folder contents that a docker is using(this is probably a better question for the docker engine subforum, sorry!)

 

And thank you for telling me the location

... I set the 'appdata' folder to cache only. Which the mover is said to not touch that folder. Could I create a custom folder, say 'downloads' in that appdata folder within the cache disk and then have stuff downloaded there to be protected by the mover? Or will the mover only refuse to touch the folder contents that a docker is using(this is probably a better question for the docker engine subforum, sorry!)

Mover will only move user shares that are set to Use cache disk: Yes.

 

The contents of any top level folder on cache or any array drive is automatically aggregated into a user share named for that folder. If you don't configure a user share, it has default settings, which include the setting Use cache disk: No, and so by default will not be moved.

I'm trying to add in this line to the config/go script from a thread here

 

- http://lime-technology.com/forum/index.php?topic=10027.msg95446#msg95446

 

So to disable the mover, it says I need to add in the line

 

"mv /usr/local/sbin/mover /usr/local/sbin/mover.old"

 

Into that config/go script. I just don't know where this script is or how to access it

 

Is this still the accepted way to disable the mover or should I do it a different way?

 

I do not encourage these kind of solutions for two reasons:

 

1. On a properly set up system there is NO reason to disable the mover, when there is nothing to move it won't do anything. Even more, disabling the mover may cause hidden problems. Any incorrect share settings go unnoticed and it becomes impossible to use the file distribution system of unRAID itself.

 

2. Doing things in the go file are considered workarounds nowadays and should be avoided as much as possible. Today we have plugins and dockers to do what we want. These can be installed and removed in a controlled way, something impossible for the go file. Leaving things in the go file can even cause unexplainable corruptions/interference with the new approach, making it hard to troubleshoot.

 

In summary, there is absolutely no good reason to do this. Anything you hope to accomplish by disabling mover can be better done with share settings. If you need further advice about share settings just ask.