Control: retitle -1 memlockd service is not enabled under systemd, while it is under sysvinit
Hi, Michał Zając wrote (04 Jul 2013 17:08:04 GMT) : > By applying the attached patch, systemd users will enjoy a fully working > memlockd on their machines: it will get enabled and started properly > It would be awesome if you applied the patch for your next upload! systemd is the default init system, so this is actually a regression in memlockd, compared to sysvinit days. I suspect this deserves slightly higher than "normal" severity, but anyway, let's fix it regardless :) Russell, how about I test the attached patch in various situations (at least initial installation, upgrade, removal and purge) and NMU once happy with it? Cheers, -- intrigeri
