I have a strange problem using this script (the latest version 1.6.6). I run unraid 5.0-rc8a on a full slackware 14 distro.
in my /boot/config/go i have:
/usr/bin/cache_dirs -d 5 -m 3 -M 5 -w
After the boot the cache_dirs script takes up 99% cpu in the foreground. Preventing my other bootscripts to run.
When I login on ssh and try to stop it using cache_dirs -q, i get the message that its not running. And indeed there is no lock file at /var/lock/cache_dirs.LCK, but the process is running.
I can kill the script. And than my boot scripts continue (starting sickbeard etc.)
When i run it in the foreground i get the following output:
I guess this happens because i rebooted, so there is still a line 'kernel: mdcmd (11): stop' in the syslog
The script does work when I use `/usr/bin/cache_dirs -d 5 -m 3 -M 5 -w -F -B`.
Any suggestions on how to fix this?