dmacias

Just not a fan of giant static builds. It's probably bigger than python with all the depends included. Especially since it wasn't built for slackware specifically either. Just feel this belongs in a docker or plugin with the correct slackware dependency packages.

There is a official docker for telegraf. https://hub.docker.com/_/telegraf There are slackbuilds but no one has it built. Not sure what depends it would require either or the database portion. The official docker page explains how to monitor the host system by mounting /proc.

Do you have PWM fans?

Sorry I'm not familiar with the Intel implementation of IPMI. It could be you don't have PWM fans. It may be the fans aren't even controlled by IPMI. They may be controlled by the bios. If that's the case there's another plugin for that

I don't find anything for slackware on this.

Reclone was never added since there's a plugin and docker. Ffmpeg requires dozens of other packages which is outside the scope of this plugin. This plugin is for adding mostly stand alone packages.

This plugin wasn't set up to differentiate between different build numbers for the same package version. That's the last number at the end of the package name. E.g. The 2 in utempter-1.1.6-x86_64-2.txz. Preclear uses an older build. Run this if on 6.7 otherwise change to your unraid version upgradepkg /boot/config/plugins/NerdPack/packages/6.7/utempter-1.1.6-x86_64-2.txz

It's probably a plugin that installs a different version. I think preclear uses utempter.

Which packages?

I added utf8proc. You'll have to install that too. Also update irssi and perl

Added bluez back in

I updated irssi. Try now.

First this plugin is not meant for running on a main server all the time. It was meant for compiling packages. I use it on a virtual machine of unraid to compile packages for NerdPack. The plugin itself should not need updating frequently. I update the packages themselves on github and that's reflected in the plugin. It's not DevPack plugin itself that's the problem, it's whatever packages they might have had installed. And since they didn't say what packages they had selected or what version of unraid they were coming from, I have no idea. I should make it not install any package if unraid is updated . But you really should unselect all packages before upgrading unraid. The core included unraid packages that are present in DevPack are all stripped of their install scripts and binaries and included only headers. I just updated all the included unraid packages to reflect 6.7.2. I haven't looked at updating any of the compiler packages. I just used it with everything installed to compile borgbackup. So it worked for me on 6.7.2.

I think this was fixed if you removed msgpack and reinstalled it. But anyway I updated borg to 1.1.10 and remove the msgpack package since "borgbackup 1.1.10 bug fix release (now bundling msgpack)" You may want to remove msgpack first then update but it shouldn't matter.

updated to python3.7

I'm not sure that's available for slackware. At least I wasn't able to find anything. I can still add figlet and lolcat if you want.

I did add this back in on 5/14. Just posting in case you missed it.

I updated node to 8.12. node -v works for me

I removed it for now until a non gtk packaged is found if even possible. That would require a desktop and a ton more packages.

Added

Added unison

1) 30s or 1 min is probably fine but constant polling of bmc and hard drives can affect performance adversely. 2) Yes. It will only take in to account the temp sensor you set to monitor. If you just wanted to control CPU fans based CPU temps, you'd be better off letting the BIOS smartfan/BMC control the fans. Unless you wanted to have more control than smartfan allows. Like min/max fan speeds. 3) The fan control script shouldn't really present and performance issues. It doesn't use much CPU and only 150-200 MB of memory of I remember correctly. The original intent of the fan control was to allow controlling a fan based on hard drive temps. Using the BIOS smartfan temp control only took into account CPU or system temps. So for me, during a parity check or rebuild the CPU temps wouldn't go high enough to make the fans spin fast enough to cool the hard drives.

It's not a matter of the plugin supporting non PWM. It's that the BMC usually can't control them and they don't respond to IPMI commands. You may be able to use the other Fan Control plugin but I doubt it. In my experience the Asrock Rack boards will only control PWM fans even through the bios smartfan control.

I just haven't had time to figure that out yet.

I added git back in