| View previous topic :: View next topic |
| Author |
Message |
Ema64
n00b
Joined: 19 Apr 2015
Posts: 19
|
 Posted: Thu Aug 27, 2015 10:41 am Post subject: Systemd and sensorsd daemon |
 |
|
Hi,
I've a problem with the configuration of the sensorsd daemon (systemd service named sensord.service). First of all: the kernel 4.0.5 finds all of my hardware sensors including fans; lm_sensors reports an unsupported chip (Nuvoton) but I forced modprobe and everything appears.
The question is: systemd sensord.service will monitor everything. I check in systemd Gentoo guide to pass custom parameters but I've found only notes about environment variables (or the apache2 memorylimit: cool example but if someone doesn't know apache how to understand?  ) and I do not know the ENVs used by sensorsd daemon. So I tried to define the exact chip to be checked by setting a variable in a custom file in: /etc/systemd/system/sensord.service.d and then I modified the original .service file in /usr/lib by passing the variable as input parameter (in the exec line I put $ARG1 as first argument).
Ok then the 'systemctl show' command into the argv[] line got the variable name $ARG1 but in the journal my chip appears one time only at the service launch then another one in alarm appears every minute (the other one is in alarm because not configured in lm_sensors as not supported).
So in desperation I followed the guides to set the ignore flag in all the etc/hellish/lmsensors/damn/configuration files  but nothing change: the systemd service continues to monitor what it likes.
The solution of course is to remove the second chip from lm_sensors but I really hate this solution and it is not a solution after all 
Could someone help me?
Thank you very much. |
|
| Back to top |
|
 |
eccerr0r
Watchman
Joined: 01 Jul 2004
Posts: 9677
Location: almost Mile High in the USA
|
| Posted: Thu Aug 27, 2015 6:40 pm Post subject: |
|
|
I haven't tried setting up sensord in systemd (because ACPI ate the sensors on my box), but it seems that there are two parts - lm-sensors.service and sensord.service ... Should the first one be configured to load the right modules?
Is there a /etc/conf.d/lm_sensors ? Is there anything in it to tell it to load extra modules, perhaps
HWMON_MODULES="your_chip_module_name"
?
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
| Back to top |
|
|
Ema64
n00b
Joined: 19 Apr 2015
Posts: 19
|
| Posted: Fri Aug 28, 2015 9:30 am Post subject: |
|
|
| eccerr0r wrote: | I haven't tried setting up sensord in systemd (because ACPI ate the sensors on my box), but it seems that there are two parts - lm-sensors.service and sensord.service ... Should the first one be configured to load the right modules?
Is there a /etc/conf.d/lm_sensors ? Is there anything in it to tell it to load extra modules, perhaps
HWMON_MODULES="your_chip_module_name"
? |
Thank you for the suggestion. My problem arose for the reasons you spoke about: it seems that systemd ignores the configuration of lm-sensors. The first service, lm-sensors.service has an entry like that in the journal: 'Started initialize hardware monitoring sensors'.
The second service do the job only at service launch, then ignores the configuration and it continues to report only the chip in alarm (of course it's lm_sensors missing support and not a real alarm ).
I configured both HWMON_MODULES and also I setup the 'ignore alarm' into the sensors config file: /etc/sensors.d/sensors.conf.
So here is the problem: also with configuration OK why systemd ignores that? In Google I found systemd execute service in a very soft and standard way: to customize them it must be overwritten the original .service file but I'm not sure of the update I should do because the one I tried didn't do the trick |
|
| Back to top |
|
|
|
Other Things Gentoo
