dlandon

There is, but it is not addressed by this forked plugin. This forked plugin adds the fruit config that is already managed by Unraid - when not needed and potentially twice: [isos] browseable = No comment = ISO images path = /mnt/user/isos valid users = ********* veto files = /.Recycle.Bin vfs objects = catia fruit streams_xattr catia fruit streams_xattr recycle <= fruit potentially added twice write list = ********* recycle:exclude_dir = ".Recycle.Bin" recycle:exclude = *.tmp recycle:versions = Yes recycle:minsize = 1 recycle:touch_mtime = No recycle:touch = Yes recycle:keeptree = Yes recycle:directory_mode = 0777 recycle:repository = .Recycle.Bin fruit:encoding = native This plugin adds the "/etc/samba/smb-fruit.conf" extra settings to the share configuration regardless of the "Enhanced macOS interoperability:" setting. If it is set to "Yes", this plugin adds the extra settings a second time resulting in duplicate vfs_objects. This is an inappropriate samba configuration and could result in redundant operations and issues. There don't seem to be any other changes made by this plugin to the share configuration, so it's unclear as to what's been "fixed". If having those vfs_objects added appears to fix the samba fault, it is a fluke because that is not the solution. The issue is in how samba handles the repository. The older versions of samba were a bit more tolerant of inappropriate confiuguration settings. The newer versions of samba are stricter about the configuration settings. I discourage the use of this forked plugin as it does nothing to address the issue amd may in fact cause problems.

The malloc assertion botched message is either there was not enough memory to fulfill the request or there is a bug in preclear. Unfortunately, the current preclear script uses a buffer file in the tmpfs ram file system to read and write disk data. Most of the time this shows up as not enough memory that preclear detects and it stops running when preclear sees there is not enough memory. The size of the buffer depends on the disk size and with a bigger disk that can be extremely large. The preclear script needs to be rewritten to do reads and writes without using a memory buffer. I removed the read after write check some time ago that verified that zeroes were actually written to the disk during the write cycle as it was time consuming (the preclear time was about 2X a write cycle alone). The cycle was write zeroes and then read the disk and verify zeroes were written. The read has to insure the actual disk was read, and not the disk buffer. This takes time - at least one revolution of the platter, maybe more for the read after write. I did not get back to to remove the buffer file use as it is a major rewrite. With newer model disks, the cycle should be: Optionally do a pre-read, but don't verify zeroes were actually written. Write zeroes to all sectors of disk without any errors appearing. Don't use a memory buffer. Check SMART report for disk problems while writing to detect a failing disk before a complete write cycle is finished saving a lot of time. Write a preclear signature if disk does not have issues. Optionally do a post-read, but don't verify zeroes were actually written. Modern disks will report issues with reads and writes and show in the SMART report things like pending and uncorrectable sectors that indicates problems. The disk that is hanging is probably a bug in preclear.

The amd-pstate-epp is the only driver that does not allow control of the "AMD Power Boost". I agree the UI should say something about this or give some indicaton it can't be controlled. I was working on implementing this driver just as the plugin was transitioned to Lime Tech. There were some things I wasn't able to complete. Hopefully Lime Tech can make some changes to help with this situation.

The acpi-cpufreq driver is a generic driver that allows controlling the "AMD Performance Boost". The amd-pstate-epp is a newer driver that controls the "AMD Power Boost" on it's own. That's why the selection of "AMD Power Boost" does not show as a selection. It cannot be set by Tips and Tweaks. It is not a bug in Unraid or Tips and Tweaks. It's how the driver works. The CPU frequencies will not be controlled the same way by each driver. You can't compare operation between them. The amd-pstate-epp driver is supposed to be a very efficient driver for AMD CPUs. There are two governors that favor either performance or power savings. "Balanced Performance" - Set all CPUs frequency scaling to balanced_performance. Prioritizes higher performance while still considering power efficiency. Good for general use with a performance bias. "Balanced Power" - Set all CPUs frequency scaling to balanced_power. Prioritizes energy efficiency with sufficient performance for most typical workloads. Ideal for minimizing power usage. I would suggest using these governors and not be concerned with the "AMD Performance Boost". It takes care of itself.

Go to a command line and post the output of this command: /usr/bin/cpufreq-info -d on Unraid 7.0.1 and 7.2.2.

I don't know. Try the Zoneminder support forum. It works with Intel and Nvidia graphics cards.

Looks like it's no longer in apps. I didn't remove it. Just ignore the warning for now.

I see the problem. The DiskActivity.page was intended to be used as a tab of the "File Activity Settings" and depend in it to load the file activity config settings. It was not intended to load as an independent page. There will be a fix for this in the next release.

Ah yes, I don't report directory operations because the cache directories plugin will keep directory operations from spinning up disks, hence they are not reported.

The 'create' event already included covers file and directory creation.

T There noisy log does not cause the log to grow out of hand, it just clutters it so it is hard to read. The inotify logging allows only 2000 lines and is checked as entries are added to the log to be sure it does not get out of hand. I'm comfortable adding an option to the settings. Look for an udate tomorrow.

That is beyond the scope of what I originally had in mind for this plugin, but with that said, I could add an option to monitor 'open' events with the caveat that it could be very noisy in the log. Let me take a look.

This plugin concentrates on disk operations that cause a disk write. Read/open events won’t give a reliable spin-up detection and will produce a lot of noise in the log. That's why I removed it. The cache directories plugin can help keep disks from spinning up from directory operations. What is your use case where you'd like file open operations logged?

The author has not set a max version in the template: The author (or moderators of Community Applications) of the plugin template (https://raw.githubusercontent.com/dlandon/libvirt.hotplug.usb/master/libvirt.hotplug.usb.plg) has specified that this plugin is incompatible with your version of Unraid (7.2.1-rc.1). It was set by a moderator. It is compatible.

Use the manual method here https://forums.unraid.net/topic/57801-support-dlandon-owncloud/#findComment-566488. The built in update hasn't worked for me for a long time.

Try a forced update. If that doesn't work, recover from a backup and re-start Zoneminder.

IMPORTANT UPDATE NOTICE In the next few days I will be updating the ownCloud Container and you need to prepare for this. You need to do the following: Read this post about the update: https://forums.unraid.net/topic/57801-support-dlandon-owncloud/page/18/#findComment-1571314 Decide if you want to accept the update or stay with the current Container. If you choose to update, be sure to make a backup of your appdata/ownCloud folder.

I wasn't sure if anyone was still interested since the USB Manager can do USB attachments.

It is now.

That FCP message is because the plugin is not in CA and FCP warns that it may not be compatible because of that.

I've made an update because Unraid is making UI changes. I use this plugin myself because of its simplicity. You are free to use it.

Another release today. I haven't used the zmeventnotification for a long time, and it seems several ZM changes broke the pushover api. I've fixed that now and added a sound configuration to the zmeventnotification.ini so you can set the sound notification for all pushover events, or per monitor pushover events. Note that the credentials for pushover are different in the secrets.ini file.

I've just released a new version of Zoneminder. The docker build has been redone to be more up to the current build methodology of dockers. The original build script was done a long time ago and needed updating. The most notable change in this release is the ability to use Intel hardware acceleration. The first post descrides how to enable the Intel hardware acceleration in Zoneminder.

You shouldn't change any permissions. ownCloud is very particular about permissions and manual changes can cause problems. I recommend you set the advanced view on the dockers page and click on "force update". The docker container should fix permissions on most everything in the /config directory when it does a first start.

Edit your config.php file: nano /config/www/owncloud/config/config.php and confirm the following: 'datadirectory' is set to 'data' set 'file_system_check_changes' to '1' ownCloud should over time scan and add the files found. It's not immediate. I haven't done this for quite a while, but when I last did it, it worked.