Service questions with systemd/systemctl

T.C. Hollingsworth tchollingsworth at
Wed Nov 16 06:02:40 UTC 2011

On Tue, Nov 15, 2011 at 4:29 PM, Alex <mysqlstudent at> wrote:
> Hi,
> I have a fedora15 system and I'm having trouble trying to figure out
> why a few services don't start through systemd. Specifically,
> lm_sensors:
> # 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

"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.


More information about the users mailing list