shinji257

Click the file then download the raw link. What you probably saved was the GitHub page that basically says it is a binary file.

Audit relies on functions included in the Slackware sysvinit package for the startup script. I've grabbed the package and cleaned it a little for unraid so it doesn't bother to create redundant rc.[1-6] folders in /etc/rc.d. It focuses on /etc/rc.d/init.d and the /etc/init.d symlink + dependent binaries. And yes it works once that is included.

Since this plugin is depreciated I've started to build my own Slackware packages using SlackBuild scripts. They are being uploaded to a github repository for anyone to use. Send me a message if you want the link as I do not know if I can post it here. Requests are accepted. I'm also going to rebuild the packages from NerdTools so they are as up to date as SlackBuild has them.

I recently added this: I was hoping that I could have the Recycle Bin show up per user folder (where it looks like it is for the share for the user) or for the baseline homes share itself. It doesn't appear to work as configured. Also the setting to toggle if the Recycle Bin is hidden or not doesn't seem to work. I went back and implemented the Recycle Bin in a slightly different way that allows pretty close to what I want.

Is there a way to get this to work for the "homes" share as well? I setup a homes share with a script to create a user specific folder in there named home when exposed to the end user. I can setup the recycle bin manually in the home share as defined in smb-extra but it won't show up in the Recycle Bin UI. homes share is added to Unraid to basically create a storage location. smb-extra has a definition for a home share that calls a script and creates a folder for the user (if it doesn't exist) at /mnt/user/homes/$user then sends the share information to the user pointing to this folder as $server/home If I edit this to add recycle bin data then the user gets their own Recycle Bin folder at that level but the plugin doesn't show anything regarding it.

A couple of things I've noticed * If you right click a dat and click Open Directory the application crashes. * If you click the link icon in DatVault that would normally bring up the website for the dat in question it crashes. * While it is scanning or repairing the box that comes up doesn't auto scroll down and scrolling left and right does nothing. You can resize it though using the corner revealing the rest of the columns. I honestly don't expect the first two to be fixed but I thought to at least get it out there for others to be aware of.

Just curious but is there a reason that /var/run/docker.sock is mounted inside the container? On the original instructions the only place that it is added is for watchtower and that's a different container. I removed it from my install and the container is operating fine.