On Wed, 2015-04-15 at 16:48 +0200, Michal Schmidt wrote:
> systemctl mask user@0.service
That off switch may work better, I'll try it when I have time to
squabble with the thing again, thanks.
user@0 was disabled in yast (suse admin tool) by me, yet found to be
in state disabled+active upon every boot. Just as yast did, systemctl
status reported it as being both disabled and active, which led me to
the conclusion that someone other than me controls this service.
-Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
