Bug#800521: systemd: sys-kernel-config.mount not functional
biebl at debian.org
Wed Sep 30 15:09:18 BST 2015
Am 30.09.2015 um 16:04 schrieb 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
> Description=dlm control daemon
> Requires=corosync.service sys-kernel-config.mount
> After=corosync.service sys-kernel-config.mount
> 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.
>> 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.
Sure, but why don't you load the dlm + configfs module not via a
module-load.d snippet, knowing that the Debian kernel doesn't have it
>> 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.
See the upstream bug report you referenced:
Either the module should be compiled in, or software requiring it should
make sure to load the module itself, ideally by shipping a
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: OpenPGP digital signature
More information about the Pkg-systemd-maintainers