Squid

Can't remember off the top of my head if I put the time of execution in the logging for the start / stop scripts (not at home at the moment). But if the scripts logs available through user.scripts shows only a single execution, then its not unRaid.

I'll ask dlandon about what changes powerdown 2.23 made that fixed this, but at first glance, I would think that it is coincidental. Nothing in user scripts should cause a mount to disappear...

There's a docker faq about that Sent from my SM-T560NU using Tapatalk

Until pauven releases his 6.2 revamp you would install my hack to make the original script work under 6.2. Ymmv however with using the hack as it does not take into consideration the new tunable that 6.2 offers. (But it won't mess up your system) Sent from my SM-T560NU using Tapatalk

Sometimes there are two sides to a question and they both deserve equal consideration. And sometimes one side is just true and the other side is just nuts. It's OK to be biased for the truth. Well said! +6.2 Thanks guys, you brought a tear to my eye [emoji25] Sent from my SM-T560NU using Tapatalk

There's an entry in the docker FAQ about making a template Sent from my LG-D852 using Tapatalk

Fundamentally CA doesn't do anything that can't be done via the base system and surfing the all applications thread. But it does it a ton better with far less agravation. The way that I look at it is even limetech in the 6.2 manual tells you to install CA if you want to run anything other than what's available from limetech themselves. Additionally CA will handle things like backups etc that can't be done easily without it. But then again, I'm also very biased here. ? Sent from my LG-D852 using Tapatalk

I have been looking for this as well. If the majority don't care then I will have to live with it, but I've been trying to turn it off since it started showing up. Go to general settings and you can turn it off Sent from my LG-D852 using Tapatalk

Cool. I always thought it was powerdown that added that Sent from my LG-D852 using Tapatalk

Easiest way is to set up a user script for the user scripts plugin to save it at array stop. I'll bang one together later today Sent from my LG-D852 using Tapatalk

I've made a test and it works. You need to put the statement: $_SERVER['DOCUMENT_ROOT'] = "/usr/local/emhttp"; In front of the require_once statements in your standalone scripts, and you are good to go. Once you have updated, I am going to remove the hard-coded path. FYI for anyone else interfacing with dynamix include files, that line needs to be added to just about everything. The above statement is not necessary anymore. I made a fallback mechanism in the modules themselves. Squid, you may want to revert your changes, sorry! Couple days. Living in hotel for a few Sent from my LG-D852 using Tapatalk

Since it looks like that sets up a cron to do it you would set that to run at startup Sent from my LG-D852 using Tapatalk

It's stored in RAM so it's lost with every boot Sent from my LG-D852 using Tapatalk

the space in the volume name is the issue, i'm not sure what the fix is for that regards unraid and docker other than don't use spaces in linux folder names. The original post got deleted, but the fix for spaces in volume paths under 6.1.9 is to check for plugin updates and install the webUI update available

I've made a test and it works. You need to put the statement: $_SERVER['DOCUMENT_ROOT'] = "/usr/local/emhttp"; In front of the require_once statements in your standalone scripts, and you are good to go. Once you have updated, I am going to remove the hard-coded path. FYI for anyone else interfacing with dynamix include files, that line needs to be added to just about everything.

Read the faq entry. Nothing to worry about Sent from my SM-T560NU using Tapatalk

At least you are going to have a very productive weekend. Good luck! When don't I.... I had my week or two off from updates, and now I'm back to my normal schedule of a new feature every other day

I've made a test and it works. You need to put the statement: $_SERVER['DOCUMENT_ROOT'] = "/usr/local/emhttp"; In front of the require_once statements in your standalone scripts, and you are good to go. Once you have updated, I am going to remove the hard-coded path. Side question: Does this have any side-effects on stuff called via the UI? I didn't notice anything with FCP since scan.php can be executed either way (kinda) but would drop my testing time significantly with CA since I have to do everything three times (with bleeding edge and without, and with 6.1.9) That's the whole point, when executing a script in CLI (standalone) mode it is not possible to pass on server settings, hence the statement to mimic. In other words there won't be any side-effect calling your script via GUI or directly. CA updated. Doesn't have the other thing we were talking about, but that'll be done tomorrow (tons and tons of testing required on it)

You guys leave me sleepless... The good news: https://raw.githubusercontent.com/bergware/dynamix/master/unRAIDv6/dynamix.bleeding.edge.plg This is version 2016.09.16 and works with unRAID 6.2 stable. Copy & paste the URL above into the install box of plugin manager. Minor nitpicks on bleeding edge: In tabbed mode, IMO its weird that the button to toggle views still appears on the Array Operations tab but does nothing (nothing for it to do but I just don't like it) With UD installed, the button is still there also, but you can't even click on it.

I've made a test and it works. You need to put the statement: $_SERVER['DOCUMENT_ROOT'] = "/usr/local/emhttp"; In front of the require_once statements in your standalone scripts, and you are good to go. Once you have updated, I am going to remove the hard-coded path. Side question: Does this have any side-effects on stuff called via the UI? I didn't notice anything with FCP since scan.php can be executed either way (kinda) but would drop my testing time significantly with CA since I have to do everything three times (with bleeding edge and without, and with 6.1.9)

Same exact issue w/6.2. I ended up getting a 1TB SSD as my cache, but now I can't do any docker items on Unassigned Devices (I had two, one for all apps except Plex (120GB) and one for Plex alone (480GB, so my metadata / thumbnails could take as much space as possible). I'm glad I can have multiple Cache drives now. After a previous update I had issues as well, so I'm just moving all my SSDs to Cache Drives and going from there. docker.img has to be on the cache. You should however be able to keep the appdata for whatever you choose on a UD device. Just change the Mounting Mode for the host path from RW to be RW:Slave

Man I got hit with this. Scared the crap out of me to find a fix since nothing would start up after this update. Fixed it now. Yeah, since everything was working properly under 6.2 beta/rc (with it not upgrading 6.1.9), everyone involved assumed there wouldn't be an issue with 6.2 final. But there was another change to the infrastructure of the 6.1.9 release that caused a snowball effect. Fixes are already being implemented to prevent it from ever happening again in the future.

I've made a test and it works. You need to put the statement: $_SERVER['DOCUMENT_ROOT'] = "/usr/local/emhttp"; In front of the require_once statements in your standalone scripts, and you are good to go. Once you have updated, I am going to remove the hard-coded path. FCP is done an updated (and tested on 6.2 / 6.1.9 with no apparent problems - Can't however easily test the docker stuff on my 6.1.9 box so I'll have to take your word for it that this won't have any repurcussions on 6.1.9) CA's testing is far more involved however before that ever gets released to the wild...

There's an entry in the docker FAQ about this Sent from my LG-D852 using Tapatalk

I've also posted in the CA thread about this. Pointless for me to update CA to disallow this, because most users would get the CA update via auto-updates at which point the UI will update also. Easiest solution is to pull the update for dynamix