This is true. I installed the 2.2.0d version which you had linked a few pages back and saw this morning that an update was available in my plugins tab. After running the update I now have 2.2.1 installed. Looks like the cache_dirs plugin should automatically continue with your branch when you push updates.
I asked about that a few posts back. It’s my understanding that (at least in my case) I have the official version which was installed through CA and the link that @Alex R. Berg has posted is for a branch.
Looks like I jumped the gun with this report. I reverted back to 6.6.2 to see if this issue was still present. It wasn't. Now I have re-installed 6.6.3 and the issue appears to no longer be present with this version as well. Perhaps there was some problem with my initial installation of 6.6.3???
Since I can't reproduce the issue I'm changing status to closed.
Yeah. The hardware is old and I can’t install any recent macOS versions. I’m guessing that something in the most recent Linux kernel has caused a compatibility issue.
I posted in general support regarding this issue.
After updating to 6.6.3, I discovered that I had to force SMB shares to unmount using sudo umount -f if I had written any files to the share from my Mac desktop running macOS Sierra (10.12.6). Downgrading to 6.6.2 corrected the issue, so it would seem to be caused by changes to SMB in the 6.6.3 release.
This diagnostic was taken after attempting to unmount a share and then forcing the unmount. Not sure if there is anything useful in it or not.
brunnhilde-diagnostics-20181021-2230.zip
Well then I’m guessing this probably isn’t the cause of my broken pipe errors since I don’t have it installed. Or was the typo in the official version as well.
How long does this usually take? I have 2.2.0 j installed and still not seeing an update on CA. Don't really want to do a manual install when I’m on a VPN from my iPhone. Too easy to screw it up.
I have a bash script in a share that I want to run on a cron schedule.
/mnt/user/odin_backup/OdinBackUp/odin_backup.sh
Is there some way to use this plg to run the script?
Perhaps it’s waiting for the polling? My polling is set at 3 minutes for HDD’s and maybe I’m just not waiting long enough. I’ll give it more time next time I reboot.
I've noticed that when fan control starts (typically after reboot) it sets all fans to high speed. I've been manually adjusting the low temp threshold to make the fan speed adjust to a proper setting. I'm wondering if there is a problem here or if I just need to wait for some event (polling maybe)?
Also, if you're going to run the script from terminal via screen, any location on the flash will work as long as you know what it is. I just use a "scripts" folder at the root of the flash drive.