(resending because gmail.com sent it as html email first time around) Hi, On Thu, Dec 8, 2016 at 6:24 AM Karel Zak <kzak@xxxxxxxxxx> wrote: > > We had positive feedback about it from Red Hat PAM maintainer, but it > would be probably better to discuss it with PAM upstream. This change > will require a new stuff in PAM API. Pretty sure Tomas is one of the upstream maintainers, but you're right, discussion should take place upstream. > Although I'm not sure why we need systemd as mediator, would be > possible to read the environment setting directly by login(1)? Or it's > expected that something (e.g. script) will be executed to get the session > initialized? The point is, the environment of systemd --user services and processes started inside a logind registered session should get the same environment. It doesn't really make sense for them to get out of sync. login(1) could try to read all the same environment configuration files as systemd, but systemd gets its environment from a variety of places (user.conf / systemd service files / /etc/environment.d), so I think getting the environment from the user manager is the best way to go. --Ray -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
