gfjardim

1) You can't. Scripts setup are tied to the mount routine, so they are defined on a partition basis, e.g., you can have more than one script running on each disk mount/unmount (one per partition). This could be changed in the future, if someone explain to me a better way to do it. 2) You can't. As I explained earlier, the mountpoint is defined according to the following preference order: user setting>label>disk ID . The script must support SATA too, so it would be a hack to define the mountpoint on usbslotX format. I don't have plans to support LVM, MyKroFt, since it's a lot of work and it doesn't quite fit in this plugin mission. But thank you anyway! All done. Thanks for your suggestion.

Guys, I'll add two new features in this plugin: "precleared" disk detection and empty disk format. Which filesystems you wish to be supported?

I fuc&$# up the package ... Everyone that updated to 2015.09.07, [glow=red,2,300] PLEASE DO NOT UPDATE IT AGAIN[/glow]; instead, remove the plugin and install again. Then, you should remove the Documentos share that was created by accident. For those who skipped 2015.09.07, the current version is 2015.09.07a . Sorry for any trouble.

Thank you, dlandon, for your support and many thanks to Napryc for the bug report. It's all fixed right now, please update your plugins.

It's compliant with 6.1 but has it's bugs.

It is compliant. It doesn't use exec.php or any executables outside /plugins/<plugin>/scripts .

Made two typos while editing config.sh file. A new version is building as we speak.

This is exported by the preclear script since bjp999 added support for myMain. I'll make some mods and submit to Joe L. again. Thanks for reporting.

Ok, this is my fault. OC now requires a certificate file on the config dir: /var/www/owncloud/config/ca-bundle.crt Fix is on the way.

I had the same symptoms after changing cache drive from one SSD to another. Seems like unRAID doesn't want to forget about the first cache device. I had to stop array, un-assign cache device, start array, stop array, assign new cache, and start array again. I don't think I had this plugin installed, but I'm not absolutely sure. The plugin uses unRAID configuration to discard array and cache disks so, if unRAID isn't saving the cache disk configuration correctly, the plugin will show it.

NAS, the mount point is only a suggestion. In fact, the order is: user mount point, label or id. One can always change the mount point if they wishes.

I set the network type to bridged, and I'm running version 8.1.1. Internet is working, despite the warning. I won't add memcache. I'll take a look on the others. I'll send a PR for the required changes to get rid of those errors, and to add memcache if you want to merge it. Memcache is a memory hog, and I really doubt it could make any difference in a SOHO environment. Already fixed the path error.

I set the network type to bridged, and I'm running version 8.1.1. Internet is working, despite the warning. I won't add memcache. I'll take a look on the others.

You need to add https://github.com/gfjardim/docker-containers/tree/templates to Docker Repositories instead.

The latest is 15.0 , and the new method of installation is not yet well proven. Eventually, I'll fix the update routine. Apparently it's working now for testing buildings. I'll try to add develop buildings again.

Ok, guys, I'm almost finishing my work on Docker Manager. I'll recap these topics and start solving some issues.

+1 vote for this as well. Will review all issues soon (finishing my work on Docker Manager).

Did you tried again in the web interface?

I think the old way. http://mirrors.slackware.com/slackware/slackware64-14.1/slackware64/d/perl-5.18.1-x86_64-1.txz Into /boot/extra .

Try running this: curl -skL http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect | perl

You have to edit the settings.json file while Transmission isn't running. The container will copy a settings.json file to /config only if it's absent.

Yep, me too.

The latest is 15.0 , and the new method of installation is not yet well proven. Eventually, I'll fix the update routine.

JUst update it to be compliant with unRAID 6.1

1) No particular reason, just never saw anyone using cron with ownCloud. Any reason to do it? 2) I'll take a look into it. 3) no EDGE function actually; I removed it after a lot of users have problems with it. Nice to know. Any links to the issue?