Ray Strode wrote:
From: Ray Strode <rstrode@xxxxxxxxxx> If the user is using a systemd system, then its useful to grab the environment from the systemd user manager process. This allows administrators to initialize the environment of the sessions via systemd configuration.
--- Isn't pam_env supposed to allow setting vars in setting up a user's first login session? (from /etc/security/pam_env.conf) # This is the configuration file for pam_env, a PAM module to load in # a configurable list of environment variables for an _authorized_ session. # # The original idea for this came from Andrew G. Morgan ... #<quote> # Mmm. Perhaps you might like to write a pam_env module that reads a # default environment from a file? I can see that as REALLY # useful... Note it would be an "auth" module that returns PAM_IGNORE # for the auth part and sets the environment returning PAM_SUCCESS in # the setcred function... #</quote> # # What I wanted was the REMOTEHOST variable set... As an aside, I use that to set my DISPLAY to the remote host on 1st login. It's only available when a user is establishing a session from a remote system. Calling it at other times won't have remotehost set. (basically values of REMOTEHOST & DISPLAY should be kept intact much like the TERM or LANG settigns. -- 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
