dlandon

Lime Technology.

I'm not going anywhere. LT just decided to take over the support and maintenance of this plugin, along with some other of my plugins.

This plugin is alive and well. The forked version by @EDACerton has some different functionality I feel is beyond what this plugin was designed to do. His version should actually be renamed to prevent confusuion.

I am no longer working on this plugin. LT has taken over the maintenance and support. You will need to contact them about any issues or concerns you have. Future releases will come from them, and not me.

I am no longer working on this plugin. LT has taken over the maintenance and support. You will need to contact them about any issues or concerns you have. Future releases will come from them, and not me.

I am no longer working on this plugin. LT has taken over the maintenance and support. You will need to contact them about any issues or concerns you have. Future releases will come from them, and not me.

I am no longer working on this plugin. LT has taken over the maintenance and support. You will need to contact them about any issues or concerns you have. Future releases will come from them, and not me.

IMPORTANT UPDATE NOTICE The next release of the ownCloud Docker Container will have several changes that will affect your ability to properly update the ownCloud container. Because of the Mariadb EOL cycle, it has become very difficult to build a new container using older versions of Mariadb. Mariadb has a bad habit of removing EOL versions from distribution. The other consideration is that Mariadb 10.5 seems to be the last version supported on Ubuntu Focal. This is complicated by the fact that ownCloud 10.9 and later support Mariadb 10.6. To accomodate these changes the container is being changed: Update container to Ubuntu Jammy. Update Mariadb to 10.6. Remove php 7.2 and 7.3. This was done for legacy purposes for older versions of ownCloud, but it is no longer necessary. The PHP line in the template will no longer be used. You have several options and need to make a decision before the next release of the Docker container. It is recommended to make a backup of your ownCloud "appdata/ownCloud" folder before doing anything. Upgrade ownCloud: Upgrade to ownCoud 10.9 or later before updating the container. If you are already at ownCloud 10.9 or greater, just update the container when it is available. Maintain what you have: There is a legacy container that you can install that keeps your system where it is right now. Edit your ownCloud template and change the "Repository:" line to "dlandon/owncloud:legacy" and install the legacy container. There will be no more updates to the "legacy" container. The legacy container is already available and you can go ahead and install that now and prevent an accidental update you may not want. In the long run, you should update ownCloud to 10.15 or the latest version and then update the container. You would do this by setting the Repository:" line back to "dlandon/owncloud" after updating ownCloud. CAUTION: If you accidently update the container with a version of ownCloud older than 10.9, the database will be updated to Mariadb 10.6 and you will then have to update ownCloud to 10.9 or later manually to get ownCloud working again. The database cannot be rolled back to an older version. This change will not be made for at least a month, so you some have time to prepare.

The choice to use those icons was made by the original author of UD. I thought at the time it was a bit too "folksy". If tags were added "SMB" and "NFS" would that make much difference? Do users understand the difference between "SMB" and "NFS"? Maybe more explanation on the dialog just above the warning statement? "Select the Penguin icon for Linux NFS. Select the Window icon for Windows SMB"

Tooltips are used all over Unraid. It's not just a UD thing. I do agree that ordering the icons with SMB first might make sense.

There are some issues I've identified that should help with this situation. Unfortunately I am unable to make any changes. LT has forked my plugin and I no longer have access to make any updates because LT is supporting and maintaining the plugin at this point. Since I can't make any updates, please don't take it out on me for a poorly running plugin I originally authored, but can no longer update.

Hovering your mouse over the radio icon will show a tooltip of what protocol it represents. If the protocol is not enabled, the icon is disabled.

I issued an update to the cache_dirs plugin some time ago to make some UI changes. Limetech has forked the plugin to their repository and will be maintaining it going forward.

https://raw.githubusercontent.com/dlandon/file.activity/master/file.activity.plg

Due to some personal circumstances, I am unable to keep the pace I was working with Unraid. I would not resubmit the plugin if I could not maintain it. I said I would not be able to provide a lot of support. A lot of support is provided here by other Unraid users and they do a pretty darn good job of it. I'll provide code fixes as needed. Honestly, this plugin does not require a lot of maintenance. I made the repositiories Private while I assessed my situation. Probably not the best decision, but I am doing the best I can. If anyone wants a refund, I'd be happy to refund your $0 investment. If LT chooses not to put it back on CA, that is their decision.

Please don't add any tracking or monitoring to plugins I've written. CA has the capability to monitor the number of times a plugin gets downloaded that will work for the information you want. I am not pleased with the move to tracking and monitoring that has been added to my work. I am re-opening the file activity plugin I wrote and maintained and you can remove the "revised" version and re-install my original version using the URL in the first post. It doesn't track you! I'll also resubmit to CA. I have added a new feature that will let you turn off monitoring SSD devices. Monitoring of file activity was intended to be used to monitor spinner devices and not SSD type devices. Monitoring SSDs overwhelms inotify and is probably the reason for the posts about overwhelming CPU activity. Inotify is not set up to monitor "access" file events as this again will overwhelm inotify. If you install the cache dirs plugin, access events should not cause disk spin ups. I am not in a position to provide a lot of support, but I will do what I can for anyone having issues with my latest version.

Unraid does not recognize the 'sda' device as an unassigned disk. On the UD page, click on the double arrows icon in the upper right of the page and see if Unraid will determine if the disk is unassigned. It will assign the disk device to 'Dev 1', If it doesn't work, go to the UD Settings page and set the logging to 'Udev and Hotplug', then click on the double arrow again. Once you do that, then post the diagnostics again.

Not necessarily, but if you follow the best practices, you should not be experiencing the stale file handles. There may be other users here with Proxmox experience that might be able to offer some suggestions.

The plugin does nothing but set up inotify monitoiring on the files. I have no idea how that can cause high CPU usage unless you are monitoring the nzbget activity. You should't monitor that activity.

Try restarting the recycle bin. I beleive there is an issue when restarting the recycle bin and I'm looking into a solution.

Go to a command line and type 'ud_diagnostics'. Then post the /flash/logs/ud_diagnostics.zip.

There was a recent release of UD Preclear that fixed this situation. Remove and re-install the plugin to see if it clears up the issue. Running from the command line will work, but not recommended

Post diangnostics. Be sure the diagnostics includes where the disks don't auto mount.

The activity is logged and can be seen on the share and disk page organized by share or disk depending on the page. Be sure the 'Status' in the upper right corner shows 'Running'. If you still can't get it working, post your diagnostics.