On Tue, Jun 30, 2020 at 08:14:41AM +0200, l0f...@tuta.io wrote:
> It seems you can reconstruct those "early" variables like the following:
> HOME=/home/@{PAM_USER}
>
> Or use @{HOME} directly since PAM 1.2.0.
>
> Source:
> https://unix.stackexchange.com/questions/258246/why-does-pam-environment-
Hi,
29 juin 2020 à 17:52 de wool...@eeg.ccf.org:
> The holy grail, for me, would have been a way to specify environment
> variables that are applied to all user logins, whether by console login,
> or ssh, or Display Manager, independent of the user's login shell.
> And those variables must includ
On Mon, Jun 29, 2020 at 10:37:49PM +0300, Andrei POPESCU wrote:
> So far I've settled to the snippet below in *both* ~/.profile and
> ~/.xsessionrc (inspired by a similar snippet in /etc/profile):
>
>
> if [ -d "$HOME"/.config/environment.d ]; then
> for i in "$HOME"/.config/environment.d/*.sh
On Lu, 29 iun 20, 11:52:45, Greg Wooledge wrote:
> On Mon, Jun 29, 2020 at 05:19:49PM +0200, l0f...@tuta.io wrote:
> > I'm not sure to understand what you want to achieve exactly, but aren't you
> > supposed to use pam_env for setting/unsetting your environment variables?
>
> We can only speculate
Greg Wooledge wrote:
> The holy grail, for me, would have been a way to specify environment
> variables that are applied to all user logins, whether by console login,
> or ssh, or Display Manager, independent of the user's login shell.
This is more or less what I try to achieve here. My use case i
Greg Wooledge wrote:
> As far as I've been able to determine, this environment.d stuff does
> *not* work with logins.
D'oh! That didn't occur to me. Re-reading the man pages with that in
mind makes more sense now. As you say, it seems to be implicitly assumed
in several places but not stated expli
On Mon, Jun 29, 2020 at 05:19:49PM +0200, l0f...@tuta.io wrote:
> I'm not sure to understand what you want to achieve exactly, but aren't you
> supposed to use pam_env for setting/unsetting your environment variables?
We can only speculate about the OP's actual goal, but I'll tell you
what *I* was
Hi,
I'm not sure to understand what you want to achieve exactly, but aren't you
supposed to use pam_env for setting/unsetting your environment variables?
Best regards,
l0f4r0
On Mon, Jun 29, 2020 at 10:42:51AM +0100, Thomas Pircher wrote:
> Hi,
>
> I'm experimenting with systemd environment variables. I have a file
> ~/.config/environment.d/50-default.conf where I set a few variables:
>
> > MOZ_ENABLE_WAYLAND=1
> > GDK_BACKEND=wayland
> > TESTVAR=test123
>
> However,
Thomas Pircher wrote:
> I'm experimenting with systemd environment variables.
I forgot to mention that this is on Debian testing/bullseye.
Hi,
I'm experimenting with systemd environment variables. I have a file
~/.config/environment.d/50-default.conf where I set a few variables:
> MOZ_ENABLE_WAYLAND=1
> GDK_BACKEND=wayland
> TESTVAR=test123
However, these variables are not set in my environment when I log in. I
have tried logging i
11 matches
Mail list logo
