Service questions with systemd/systemctl

Alex mysqlstudent at
Thu Nov 17 00:24:35 UTC 2011


>> # service lm_sensors restart
>> Redirecting to /bin/systemctl  restart lm_sensors.service
>> # service lm_sensors status
>> Redirecting to /bin/systemctl  status lm_sensors.service
>> lm_sensors.service - Initialize hardware monitoring sensors
>>          Loaded: loaded (/lib/systemd/system/lm_sensors.service)
>>          Active: active (exited) since Tue, 15 Nov 2011 18:25:52 -0500; 7s ago
>>         Process: 1151 ExecStop=/sbin/modprobe -qabr $BUS_MODULES
>> $HWMON_MODULES (code=exited, status=0/SUCCESS)
>>         Process: 1157 ExecStart=/usr/bin/sensors -s (code=exited,
>> status=0/SUCCESS)
>>         Process: 1155 ExecStart=/sbin/modprobe -qab $BUS_MODULES
>> $HWMON_MODULES (code=exited, status=0/SUCCESS)
>>          CGroup: name=systemd:/system/lm_sensors.service
> AFAICT sensors isn't supposed to stick around.  This is reflected
> properly in it's systemd unit file by it being configured
> "Type=oneshot".
> "man sensors" says the following about the "-s" switch:
> "Evaluate all `set' statements in the configuration file and exit. You
> must be `root' to do this. If this parameter is not specified, no
> `set'  statement is evaluated."
> modprobe is completing successfuly, as is "sensors -s", so everything
> should be copacetic.

Yes, thanks for spending the time to explain. It's working correctly.

There appears to be several voltages that are out of normal range, but
I think it just needs to tuning.

Thanks again,

More information about the users mailing list