On Mon, May 22, 2017, 16:40 Tomas Mraz <tm...@redhat.com> wrote: > On Mon, 2017-05-22 at 15:45 +0300, Mantas Mikulėnas wrote: > > On Mon, May 22, 2017 at 2:11 PM, Nikolai Kondrashov < > > nikolai.kondras...@redhat.com> wrote: > > > > > Hi everyone on systemd-devel, > > > > > > I'm trying to solve a problem of supplying locale settings to non- > > > shell > > > programs acting as login shells in Fedora and RHEL, as described > > > below. > > > > > > So far it seems the Debian way of doing things will work. > > > > > > Could you please confirm that the format of locale.conf is not > > > going to > > > change > > > in a way incompatible with what pam_env.so expects? > > > > > > > Well, the format of locale.conf is meant to be sourceable by sh/bash, > > so I > > don't expect it to ever change. It's also covered by the official > > "stability promise" [1]. > > > > A better question is what exactly pam_env.so expects... Last time I > > couldn't quite figure out when it wants a key=value file and when it > > wants > > its own special "foo DEFAULT=bar" format, and in fact the manual > > doesn't > > seem to match the actual behavior... Does it autodetect or something? > > The 'key=value' format works by accident but I plan to make it official > one day. >
Hmm, I guess the extended format in ~/.pam_environment is also allowed by accident? I still use it for setting variables which depend on $HOME or $XDG_RUNTIME_DIR (like the ssh-agent path). > -- Mantas Mikulėnas <graw...@gmail.com> Sent from my phone
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
