Package: memlockd
Version: 1.2+b1
Severity: important
Hi,
after installing memlockd on a mostly clean sid VM, the service starts
correctly, but it's not started on subsequent boots:
# systemctl status memlockd.service
● memlockd.service - memlockd
Loaded: loaded (/lib/systemd/system/memlockd.service; disabled; vendor
preset: enabled)
Active: inactive (dead)
I see nothing in memlockd.postinst about systemd
and no symlink in /etc/systemd/system/*.wants/.
It looks like the fix for #714957 only partially fixed the problem.
(FWIW, I would dive deeper and probably propose a patch if
debian/rules was more similar to what I'm familiar with, i.e. if it
used the dh(1) command sequencer, but in its current state it's too
far out of my comfort zone.)
Cheers,
--
intrigeri
