ClintSouthwood

Would it be possible to add sas2flash for HBAs?

Worked like a charm. Many thanks!

When attempting to run iperf3 I'm getting the following error: "error while loading shared libraries: libssl.so.1..." How can I add the requisite libraries? TIA

Thanks, I will check these out - they both look promising. I didn't consider using a separate container for monitoring though it makes sense. The support thread for the Munin-server container by Jugniji in CA seems to have not been updated for quite a while but there are several other templates available in dockerhub. I figured that displaying temperature readings would be a natural extension of the system stats plugin and I was somewhat surprised when I couldn't find any mention of it. Since I have both plugins currently installed and configured, I thought perhaps there was simply a configuration setting I missed to integrate the two for unified data on one display. The idea being that one could find a peak in CPU usage, say during an intensive transcode operation, and correlate the peak usage with the peak temp.

Thanks for the info, will look into this as I thought pads were generally inferior to TIM compounds. Now if only I could find a better heatsink for my mobile chip! My question still stands though, would love to have historical temp data available in some form.

For what it's worth, I noticed the same thing (the path was not populated by default) but it does exist in my container.

I currently have both Dynamix System Stats and System Temp plugins installed and they work great. Many thanks. Apologies if this has already been asked but my search didn't turn up anything. Is there any possibility to integrate historical system temperature data into the System Stats graphs? I would love to be able to monitor temperatures over time. If not, can anyone suggest something else that can enable this functionality? Thanks in advance.

Fair enough, I do see it in the post now, thanks for linking it. I did skim this post before upgrading but obviously missed that pertinent bit. I'll certainly be more careful going forward. Still, removing current (core/key) features, no matter how "improved" they are, is pretty low, IMO. This is not new behavior from the Emby team and, quite frankly, I'm not surprised - they've been on this trajectory for quite some time now. I respect developers and understand that they want to be paid for their effort but to change the entire business model just after gaining a decent userbase (most of whom likely jumped ship from Plex for similar reasons) is disturbing. I sincerely hope that Jellyfin takes off, it's mere existence indicates that I'm not the only one upset with the transition of FOSS into a closed-source, subscription-based model. Apologies for the rant, I know this isn't the place for it.

Thank you for all your awesome builds, kind sir. Will migrate over to your container ASAP.

Mostly a lurker here but I didn't see this mentioned yet. The latest update seems to have removed the ability to use hardware transcoding for non-premium users. I really dislike the underhanded nature of placing current features behind a paywall and neglecting to mention their removal in the changelog. I've begun testing the Jellyfin fork though I had to set the docker up manually since there isn't a prebuilt one in the community apps yet.