hugenbdd

Community Developer
  • Posts

    450
  • Joined

  • Last visited

Everything posted by hugenbdd

  1. Is this link available? It is necessary for plugin developers to take appropriate action within their plugins to enable them to utilize the multi-language support. The details on what is required are covered in the design guide here. "Here" <- https://wiki.unraid.net/images/5/5e/Multi-language_Support_Design_Guide.pdf Doesn't seem to work.
  2. doesn't really tell me how to add for plug-in's. If you can post a github link of another plug-in that has translations, I will take a look.
  3. Ever thing will move because you have "Move All From Cache-Yes shares when disk is above a certain percentage:" set to "Yes" and the threshold set to 85%. You can set this to "No" however, there is a possibility you could use 100% of cache. But, if you monitor it and get your "days old" setting just right, you can keep 60 days or close to 60 days with no issues depending on how much you download each day. (i.e. You are trying to match the amount that gets moved off each night with about the same amount you download each day)
  4. the binary mover changed locations in 6.12 from older releases. For me on a slightly older release. # which mover /usr/local/sbin/mover Can you try the command which mover and post the results? There is a stop option for mover but it may not hitting the right file.
  5. I think you have some other problem going on. You should only have the names of your shares in that directory. Maybe check SABNZB config? A typical config file would have the following inside it. # Generated settings: shareComment="" shareInclude="disk1,disk2,disk3,disk4,disk5,disk6,disk7,disk8,disk9,disk10,disk11,disk12,disk13,disk14,disk15,disk16" shareExclude="" shareUseCache="yes" shareCachePool="cache" shareCOW="auto" shareAllocator="mostfree" shareSplitLevel="" shareFloor="50000000" shareExport="e" shareFruit="no" shareCaseSensitive="auto" shareSecurity="public" shareReadList="" shareWriteList="" shareVolsizelimit="" shareExportNFS="-" shareExportNFSFsid="0" shareSecurityNFS="public" shareHostListNFS=""
  6. Can you post the output contents of this directory? /boot/config/shares/ ls -ltr /boot/config/shares
  7. most logs are now stored under /tmp/Mover
  8. Check your cron entries. cat /etc/cron.d/root
  9. New Version 07-03-2023 HUGE thanks/Shout-out to @Swarles for the help with updating code fixes and adding a great new feature. You can now have some customization per share. It's great to have another forum member jump in with some good idea's and breathe some new life into the plug-in. - Add check and creation of link to new binary move location. (Allows the plugin to survive a reboot) - Fix first time save on scheduler page. (Swarles/Yamraid 6/21) - Change "move all" default setting to No to not confuse new installs/users. (Swarles) - Custom mover tuning settings for individual shares. Located at “Shares>[click share]>Mover Tuning”. Includes age, size, sparseness, file list, file types, hidden files/directories, move all override. (Swarles 6/2023)
  10. The location moved on a recent release. A new install will create a softlink. But I need to add a check to add a softlink every time mover runs. As I believe it will be lost on reboot.
  11. I figured it would help identify issues easier in the future. if we ever have to come sort through this 43 page thread.
  12. nope! I just released yesterdays fixes. next next release... #6-21-2023 - Fix spaces in before script file path (Swarles 6-18-2023) - Fix spaces in after script file path (Swarles 6-18-2023) - Fix spaces in ignore file list path (Swarles 6-18-2023) - Add check before moving to make sure file or directory exists to avoid binary mover lstat error. (DontWorryScro 6-19-2023)
  13. Usually this behavior is when you first install the plug-in. Generally you make some changes, save, then come back in and the settings should look and work correct. There is something going on with the disable javascript that I have not been able to track down.
  14. Can you DM the latest list of log files under /tmp/Mover ? There should be about 6 files. (example below) The two important ones that I will mainly look at are Mover_Tuning_<DATETIME>.log and Custom_Mover_Tuning_<DATETIME>.list Example: -rw-r--r-- 1 root root 8742 Jun 19 10:09 Mover_Tuning_2023-06-19T100928.list -rw-r--r-- 1 root root 6777 Jun 19 10:09 Custom_Mover_Tuning_2023-06-19T100928.list -rw-r--r-- 1 root root 2861 Jun 19 10:09 Custom_Mover_Directory_2023-06-19T100928.list -rw-r--r-- 1 root root 0 Jun 19 10:09 Cache_Tuning_2023-06-19T100928.list -rw-r--r-- 1 root root 0 Jun 19 10:09 Custom_Cache_Tuning_2023-06-19T100928.list -rw-r--r-- 1 root root 42798 Jun 19 10:09 Mover_Tuning_2023-06-19T100928.log
  15. Yes, since it's in tmp it will get destroyed on every reboot. I think I just need to create the directory and then sleep for 1 second before it moves on every Mover run. I'm not sure if I updated the age_mover file on github. I'll try and do that in the next few hours. (It is obviously updated in the tar package)
  16. I would need to see log files from /tmp/Mover Also, has the name of the cache been renamed at any point? Sometimes the config file is not updated.
  17. More details/additional logging info is now under /tmp/Mover
  18. New release, sorry for the releases back to back. ###2023.06.16 - Fix no empty directories file - Fix missing echo statement on hardlinks area. (Foux 6-16-2023)
  19. DM sent. Lets work this out there. Once fixed I can post the solution in the forum.
  20. Was this second run working? I believe there is a bug on the first run of Mover after installing. Second and following times it should work.
  21. No, can you verify the folder was created? /tmp/Mover from the console ls -ltr /tmp/Mover
  22. Normal mover scheduled would move them, I'm not sure if there is a way to ignore whole shares. Mover Tuning was originally written when there was just one cache drive, making it much easier... Now there's lots of intricoes to figure out. Yes, that is part of Mover Tuning. meant to make it easier to empty a share from cache.
  23. New Release (And I already found a bug which will be fixed tomorrow) ###2023.06.15 - Delete empty directories ***(Bug when no empty directories found) - Add Softlink for binary mover file change if on 6.12 RC8 in install script. (CS01-HS Found 6/13) - Add function for compatibility with RC8+ with zfs % full (a632079 - 6/3)
  24. No, settings apply to all shares. The only one that is share specific is % of disk used. I need some help with setting up gui pages for share specific settings. I would like to be able to provide this, but it is most likely a ways off. You could accomplish this by looking at the plug-in code and writing your own bash script.
  25. Yes looks like they changed locations of it for that release.