From: Linda Walsh <lkml@tlinx.org>
To: Ray Strode <halfline@gmail.com>
Cc: util-linux@vger.kernel.org, Karel Zak <kzak@redhat.com>,
Lennart Poettering <lennart@poettering.net>,
Ray Strode <rstrode@redhat.com>
Subject: Re: [PATCH] login-utils: import environment from user manager on systemd systems
Date: Tue, 25 Oct 2016 14:06:41 -0700 [thread overview]
Message-ID: <580FC961.8060502@tlinx.org> (raw)
In-Reply-To: <1477427661-19788-1-git-send-email-halfline@gmail.com>
Ray Strode wrote:
> From: Ray Strode <rstrode@redhat.com>
>
> 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.
next prev parent reply other threads:[~2016-10-25 21:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 20:34 [PATCH] login-utils: import environment from user manager on systemd systems Ray Strode
2016-10-25 21:06 ` Linda Walsh [this message]
2016-10-26 19:38 ` Ray Strode
2016-10-27 21:53 ` L. Walsh
2016-10-28 15:06 ` Ray Strode
2016-10-28 3:02 ` L. Walsh
2016-10-28 15:14 ` Ray Strode
2016-12-07 19:45 ` Ray Strode
2016-12-07 20:04 ` Ruediger Meier
2016-12-08 11:24 ` Karel Zak
2016-12-08 15:00 ` Ray Strode
2016-12-08 18:39 ` Fwd: " Ray Strode
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=580FC961.8060502@tlinx.org \
--to=lkml@tlinx.org \
--cc=halfline@gmail.com \
--cc=kzak@redhat.com \
--cc=lennart@poettering.net \
--cc=rstrode@redhat.com \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.