Tool to Control Fan - fanctl

[tuxd3v]

EDIT: With "always on" option I got the behavior i was expected, exept for that if the minimum temp is reached ats produces an load spike pushing the temp above the minimum so the fan will speed up, slow down until near stop and spin up again.

Hello TheSupercomputer,
If you push the board at full throttle, temps could be above 50C, but that's a normal behaviour, also you can tune that in '/etc/ats.conf'.

Each time you change '/etc/ats.conf', you need to restart the service, don't forget that..

Here is a output, of mine, at full throttle..

You can see all cores are at 100%..they are like that for one year, testing ATS tool..
and there you can see the CPU Utilisation of ATS since last restart:

Code:

# ps -L -F -p 585
UID        PID  PPID   LWP  C NLWP    SZ   RSS PSR STIME TTY          TIME CMD
root       585     1   585  0    1   866  1516   2 May29 ?        00:00:28 lua /usr/local/sbin/ats

 It have 28 seconds of CPU used since that time, which translate to to approximately:

Code:

# Time of ATS Process( 28 seconds, running for 33 days )
~# ps -L -F -p 585
UID        PID  PPID   LWP  C NLWP    SZ   RSS PSR STIME TTY          TIME CMD
root       585     1   585  0    1   866  1516   2 May29 ?        00:00:28 lua /usr/local/sbin/ats

# Usage per each CPU Second Time( 1 second = 1000000 microseconds ):
~# bc -l <<<'28/(33*24*3600)'
.00000982042648709315 ( ~ 9.82042648709315 microseconds )

# Normalised usage in %( 1000000 microseconds = 100 % ):
~# bc -l <<<'(9.82042648709315/1000000)*100'
.00098204264870931500

So ATS is using ~ 0.00098%, or roughly ~0.001% CPU Time..
 
I haven't detected that spikes ever( you could have a increase if you are in test mode, because it needs to pint out information, and such.. but in daemon mode that shouldn't happen.. ).

My Suggestion, is to stop ATS( do it several times..like bellow ), reload units and then start it again...it could be that a previous unit is trying to restart a service that doesn't exist any more( this situation I have already experienced.. )

Code:

systemctl stop ats;sleep 2;
systemctl stop ats;sleep 2;
systemctl stop ats;sleep 2;
systemctl stop ats;sleep 2;
systemctl stop ats;sleep 2;
systemctl stop ats;sleep 2;
systemctl daemon-reload;
systemctl start ats;

Then check if everything is ok, and no more spikes.. 

Best Regards,