Yeah,  I mis quoted the pid.

 

I didn't realize that all those processes were normal.

 

alll seem to be exiting when I do a cache_dirs -q.

 

Thanks for the help

I am starting cache_dirs with the following command from an unMenu goscript:

 

/boot/custom/bin/cache_dirs -w -B -i "Media"

 

"Media" is a top-level user-share that contains sub-dirs "Movies" and "Music" (each of which contain further subdirs)

 

I have noticed while running htop that there are several (like 10!!) cach_dirs processes running.  Is this normal?  Or, am I doing something wrong?

I am starting cache_dirs with the following command from an unMenu goscript:

 

/boot/custom/bin/cache_dirs -w -B -i "Media"

 

"Media" is a top-level user-share that contains sub-dirs "Movies" and "Music" (each of which contain further subdirs)

 

I have noticed while running htop that there are several (like 10!!) cach_dirs processes running.  Is this normal?  Or, am I doing something wrong?

Read the post about two back from this..

 

There will be a child process active for each of your hard disks, one for the parent process starting everything, one to scan the disks in a repeating loop, and if you catch it at the right time, a "find" process.

 

So, you have 7 or 8 data disks in your server. 

 

If you are running one of the last few beta versions of unRAID (4.5beta7 onward) you can use the "-B" option, as you do not need the extra child processes to keep your hard disks from showing up as "unformatted" if being scanned when you stop the array.  (They are not really unformatted, just un-mounted as the array is stopped)

 

Joe L.

 

Joe L.