Bug#800521: systemd: sys-kernel-config.mount not functional

[Ferenc Wagner]

Michael Biebl <biebl at debian.org> writes:

> Why are your using a .service file to load the dlm module?

Sorry for being confusing by eliding too much.  The dlm service starts
the DLM control daemon, and also loads the dlm kernel module beforehand.
It's dlm_controld which needs a mounted configfs (and the dlm module):

$ systemctl cat dlm
# /lib/systemd/system/dlm.service
[Unit]
Description=dlm control daemon
Requires=corosync.service sys-kernel-config.mount
After=corosync.service sys-kernel-config.mount

[Service]
OOMScoreAdjust=-1000
Type=notify
NotifyAccess=main
EnvironmentFile=/etc/default/dlm
ExecStartPre=/sbin/modprobe dlm 
ExecStart=/usr/sbin/dlm_controld --foreground $DLM_CONTROLD_OPTS
#ExecStopPost=/sbin/modprobe -r dlm

# If dlm_controld doesn't stop, there are active lockspaces.
# Killing it will just get the node fenced.
SendSIGKILL=no

[Install]
WantedBy=multi-user.target

> Why does the dlm.service require the sys-kernel-config fs?

Because dlm_controld uses files under /sys/kernel/config/dlm.

> Can't you just ship a snippet in /usr/lib/modules-load.d/ and then also
> include configfs in there?

No, loading the dlm kernel module is only part of the task.

> Fwiw, I don't think there is anything to fix on the systemd side.

Do you mean that sys-kernel-config.mount somehow manages to work for you
under jessie?  Then my initial analysis must be incorrect somewhere.
-- 
Thanks,
Feri.