The SPINPID2.SH script returns syntax errors!

[collector]

Hello, I adapted this script which was developed by "Glorious1" for Debian/Ubuntu, the CPU part works very well, but the hard disk part returns syntax errors, even if the hard disk and temperature detection works.

I replaced the "camcontrol" tool by the "inxi" tool which does exactly the same job

spinpid2.sh : https://paste2.org/VG33FbD5
spinpid2.config : https://paste2.org/OWCchWmy

After some research, I found out that someone else also adapted the script on Debian, replacing "camcontrol" with "lsblk" but he gets the same syntax errors on Debian!

https://gist.github.com/havardAasen/a46c416b61279974938e3668668e9d01

Which means, that these errors are not due to my modifications!

The part of the "spinpid2.sh" code that seems to have problems is this one:

I would very much like the developer of this script or someone to help finish the Debian/Ubuntu port of this script, there is not much left except for the syntax correction on the lines above.

This script is very extremely important for my configuration (X11SSH-F)!

 

[sretalla]

Perhaps you want to look at this:

HDD Spindown Timer

ngandrass updated HDD Spindown Timer with a new update entry: Version 1.3.2 (2022-01-10) released Include an option to shutdown the system after all monitored drives are idle for a specified number of seconds. Thanks to @hschwane For more details see...

www.truenas.com

 

[collector]

Perhaps you want to look at this:

HDD Spindown Timer

ngandrass updated HDD Spindown Timer with a new update entry: Version 1.3.2 (2022-01-10) released Include an option to shutdown the system after all monitored drives are idle for a specified number of seconds. Thanks to @hschwane For more details see...

www.truenas.com

Thanks, but unfortunately, this script doesn't do the same thing as SPINPID, which monitors the temperature of the hard disks and the CPU, and then configures the fans to the right speed in real time...

We just need to find a solution to these syntax problems, and the script will be fully operational on Debian.

I really hope someone can find a solution to fix this script!