Squid

Start: wget -qO /dev/null http://localhost:$(lsof -nPc emhttp | grep -Po 'TCP[^\d]*\K\d+')/update.htm?cmdStart=Start Stop: wget -qO /dev/null http://localhost:$(lsof -nPc emhttp | grep -Po 'TCP[^\d]*\K\d+')/update.htm?cmdStop=Stop

Usually, that would mean that the appfeed lost track of sickrage temporarily (out of my control - could be that phaze made a quick change to the xml and there was an error in it). But I just installed sickrage and FCP is working.

I was having this exact issue still however your solution of mapping app data direct to a disk e.g. /mnt/disk1/appdata/unifi instead of /user/ did work for me... I would add however that simply remapping the user share and restarting the docker didnt fix it, I had to fully delete the docker image AND delete all traces of the old /appdata/unifi folders from my /user/ share, then reinstall it mapped to /disk1/ before it would work Just FYI that 6.2 would odds on fix this issue Sent from my SM-T560NU using Tapatalk

Correct Sent from my SM-T560NU using Tapatalk

It's not obvious how to if you're not used to it... http://lime-technology.com/forum/index.php?topic=32900.0 Sent from my SM-T560NU using Tapatalk

Do you have a SSD Cache drive?

Settings - Schedules

Fixes before features... AlwaysTM Fixed: CA under specific circumstances could show as not autoupdating when in fact it would Fixed: Under very specific circumstances, some plugins set to not autoupdate could Fixed: PhAzE plugins would not show up as installed if they were (due to a technical error on the .plg file vs the xml file) NOTE: All auto update settings are going to be reset back to defaults with this update. IE: Both CA and FCP will auto update, and everything else will not. You will have to adjust the settings back to what you feel is correct for your use case.

Actually rather simple, since those lines won't execute from a straight command line either. I'm sure there's a million ways of doing it, such as adding the cron via crontab, or using the AT command, etc. It threw me for a loop when I looked at the post this morning since I thought the problem was with user.scripts, and not with your script itself.

I too have been enjoying this tool, has helped with some testing I've been doing. Thanks! We're getting off-topic though, perhaps it deserves its own thread? Running the latest version - the Total column looks more like an average to me. I would have expected a sum? Is this plugin still around? The link doesn't work... Squid updated it to 6.2 here http://lime-technology.com/forum/index.php?topic=29009.msg492140#msg492140 Nowhere near as thorough for 6.2 as what the next release by Pauven will do.

I'll look into it tonight Sent from my LG-D852 using Tapatalk

Check the docker FAQ, or post #2 in the 6.2 announcement

Hidden folders do show up in the list for both source and destination

I can easily implement a backup feature like that (good idea), but only with regards to autoupdates. Updating the plugin through the plugins tab I have zero control over. Ideally, something like this should be done within the plugin manager itself, but I'll pop in the code to see if it gets any traction.

It actually will. IE: CA doesn't care how you install a plugin or a docker app. But, you just ran across an "issue" which I just found the other day (I accidentally wound up installing one of his plugins) and is on my to-do list. (And thus far, it seems to be just PhAzE's plugins affected) Namely, CA checks the URL of the plugin to figure out the application it refers to. The application feed for his plugins lists the URLs as https://raw.githubusercontent.com/..... The plugin file lists the URL as https://github.com/.... On installation, it doesn't matter as the github.com is automatically redirected to raw.githubusercontent.com, but CA misses that the plugin is installed (whether its installed via CA or not). (But funny enough, CA does know if you uninstall it to put it into the Previous Apps section... EDIT: technically, its the plg file that listing the incorrect URL, as its url is the one subject to redirection, but I'll account for it in CA. EDIT2: FCP recognizes PhAzE's plugins, but on a check of the coding, FCP is a more relaxed test to determine the plugin, and I'll have to fix that in the future.

Check out either the docker FAQ or the 2nd post in the 6.2 announcement Sent from my LG-D852 using Tapatalk

Cross over into FCP territory. CA sends out no notifications on updates available (and selectable whether it notifies that it installed one). FCP you can ignore the warning if you choose and you won't be notified, and its disableable within dynamix to send out notifications on plugin updates also. True enough. M$ has in the past taken out large numbers of people computers with an update, and in this case, one small itsy bitsy change by LT without my knowledge started a snowball effect. Luckily both parties have learned from this and implemented changes to the update system as a whole Dynamix will do this already. Not a big deal to implement this. Once again not a big deal. Auto-updates have their place in the world, and the world as a whole is moving towards it regardless of the platform. CA by default only has and only ever will (but you can still disable this) update itself and FCP. CA I highly recommend autoupdates enabled for it, simply because it is still a large moving target and constantly moving ahead either weekly or daily. FCP not so much, but since it's my plugin, I can choose whatever I feel is correct for it Autoupdating applications is not my "ideology". It is merely a convenience for users to decide for themselves to take advantage of it or not.

No fundamental reason why they couldn't be that I'm aware of

That's correct. For a separate file containing the checksums you would either have to generate them on the client using something like corz for Windows or the checksum plugin (but development ceased on that a long time ago. But it does work for me) Sent from my LG-D852 using Tapatalk

I have a issue with latest 2016.09.18c, can't edit any VM, both edit and edit XML, nothing happens after pressing update, even if nothing is changed. Uninstalling and rebooting fixed it. Made a new version 2016.09.19 available, which addresses this. Please test. FCP & CA have been updated and removed the DOCUMENT_ROOT from them

This is what I always tell her Sent from my LG-D852 using Tapatalk

In no particular order, (and hopefully not missing anyone) Gfjardim for a basic framework (which is no longer used) Kode for the application feed Linuxserver.io - hosting the Appfeed Bonienl - additional contributions and telling me when I'm doing something wrong Eschultz - additional contributions The authors of unraid's docker manager which made everything so much easier CHBMB - beta tester Sparklyballs - my nemesis Moosehead - sustenance Stompin Tom Connors - entertainment But most importantly all of the template and plugin authors without which CA Would be completely pointless. Not to mention all the users of CA. (and a VERY understanding wife who let's me spend as much time as I do playing around with CA ) Sent from my LG-D852 using Tapatalk

Thanks. I completely have up on help text which is what other authors use as there was just too much going on. And since damn near everything on the screen will do something if you click on it needed something else Sent from my LG-D852 using Tapatalk

And I'm now driving for the next 10 hours so pita for me to check syslogs Sent from my LG-D852 using Tapatalk

Another possible reason. And I'm going to emphasize possible. First off are the mounts unavailable from the command line when cp starts bitching? This could be a slave thing. Try mounting them into /mnt/disks/whatever (the only location that works with slave modes) adjust the templates to the new mount and set the mounting mode as rw:slave Sent from my LG-D852 using Tapatalk