Thanks for the very fast reply :) On Thu, 8 Mar 2018, Michael Biebl wrote:
Are you logging in via serial console as unprivileged user?
Yes. If I'm root, that grants all access and the session/tty/etc. become irrelevant. But I want to run something as not-root under systemd-inhibit. Yes, I could sudo systemd-inhibit sudo -u ... but blech :)
/etc/securetty (pam_securetty) is not really a good idea.
Any thoughts why, other than that the default version of that file seems to have everything under the sun listed in it?
That all said, you should really take this up with upstream at https://github.com/systemd/systemd/issues
ACK, though systemd's official policy is basically "go away if you aren't running the bleeding edge". I can verify the problem code is in the git master of systemd, but their policy is to not accept bug reports from such "old" versions as Debian runs, and explicitly to redirect back to the linux distro for support.
Nevertheless, filed https://github.com/systemd/systemd/issues/8582 -- -Matt "Reality is that which, when you stop believing in it, doesn't go away". -- Philip K. Dick GPG fingerprint: 0061 15DF D282 D4A9 57CE 77C5 16AF 1460 4A3C C4E9 _______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
