Squid

Drop compatibility with unRaid 6.3.x / 6.2 / 6.1. Minimum OS required now 6.4.0 Remove all compatibility code Less annoying highlights on search results Fixed reference to URL for alternative app icon image Removed Icon display mode Always have the apps displayed centered, regardless of browser width or number of results Revamp of 'Searching' info popups Removed link to announcement thread for repositories Added ability to display changelogs on plugins when an update is available Because of the skin changes (and more importantly that I'm not really in a position to test anymore on 6.3/6.2/6.1), support is now dropped for anything but 6.4/6.5

Allow unRaid's webUI to utilize the full width of your browser instead of being limited to 1920px #!/bin/bash sed -i 's/max-width:1920px;//g' /usr/local/emhttp/plugins/dynamix/styles/*.css

Looks like the template was made with an ancient and buggy version of dockerMan. The solution is this Change the network mode from Bridge to Host I'm going to pop a mod comment onto the app until such time as this gets worked out.

So that no one gets scared off, https://lime-technology.com/forums/topic/59647-support-djoss-crashplan-pro-aka-crashplan-for-small-business/?page=17&tab=comments#comment-652394

You can edit it all day long. In basic view mode, you can simply type the appropriate path, or in advanced view the Edit button will appear. On any application nothing is stopping you from adding any additional mappings. You pretty much have to anyways to access your media within a container.

It appears when you hit show more settings. Personally, I would let Radarr, etc do the moving rather than Sab, but in this case you would do something like map /complete to /mnt/user/media, and set up your Categories as DVD, BluRay, mkv etc, and tell Sab to move completed downloads to /complete

No. Possibility for the future though.

Nope. It goes through your installed / previously installed apps, determines what's not referenced any more by an installed app, and offers it up to delete. That's why there's the double confirmation before it does anything.

Finally, someone who takes the possibility of crosstalk on cabling serious

@wreave, whom I understand is involved in the development. Of which I have no problems with.

Here's when it runs: On initial install when going to it's settings * After an update when going to it's settings * 10 minutes after an array start (background) On the schedule the user selects When pressing Rescan * If a scheduled run happens before going to FCP's settings, then a scan will not happen. Put in a feature Req for errors to be logged. The test in FCP is classified as "Other" It will log the fact (if logging is enabled), but it will not trigger a notification from FCP.

LT recommendation is disabled mover logging Only the first time. After that it only rescans on your schedule or when pressing rescan

Set the # of days to keep backups, and have the frequency shorter than that. Running every 7 days and keep for 28 will always have 4 backup sets available.

Epic nobel is a container you installed, and didn't give it a name. Starbound you probably named it as such. The plugin gets its info directly from docker, and doesn't worry about how its been installed.

User scripts plugin Script would be similar to docker restart deluge

No and no. (Although you can turn on my own logging which will state when its going to skip running mover and when it does start it. No logging on when its done though.

The Backup never finished by the end of that snippet. See what happens when you manually click "Backup Now"

Good catch. I never would have noticed on my system. From my system: @limetech mdNumDisks="23" mdNumDisabled="1" mdNumInvalid="1" 23 is correct (22 data + 1 parity). Both disabled and Invalid though are incorrect. I originally did play with Dual Parity, decided against it for various reasons. Would've done a new config as what I was using for Parity 2 did get reused as a data drive. A quick glance through other user's diags shows Parity 2 status as always being DISK_NP_DSBL when not installed.

Today's update should be a quick and dirty fix. See how that goes. If it doesn't work good for you, then I'll add the download

Are you sure you're using dlandon's and not bshakil's version?

Try today's update and see if it doesn't let you see the files / folders ( You will probably have to re-run the extended test though)

Installs fine for me on 6.5.1-rc5 The error implies out of memory. @jbartlett. Since this is a java app, would it make sense to add in environment variables to limit the java memory as some other java containers have done?

Nope You would leave mover running on whatever schedule you want (say every hour). The rules for when to move are evaluated at that schedule. If you want to force all the files to move (say once a day) regardless of the rules, then you enable force and set a schedule for it. Regardless of any rules, hitting Move Now on Array Operations will always move the files. A Forced schedule only makes sense if its less frequent than the regular mover schedule. You would also get rid of the user script.

If ever in doubt about a LSI/Avagio card, contact them. They are more than happy to let you know if the card is counterfeit or not. While I would never personally buy a LSI card via ebay being shipped from China, I did however take a leap and buy a card via Newegg for $25 new that was 100% legit according to LSI

ok. I've left the forced move as a pure cron entry as, It's a ton less work, which is a big plus from my point of view If you're very astute, you can set "disable mover schedule", but also enable the forced schedule to allow you the utmost in scheduling flexibility that unRaid won't normally allow you. (If you're running this plugin, then its flexibility you want, right?) At the same time, I removed the option for Move Now follows the rules, as it didn't really make much sense in retrospect.