Re: [systemd-devel] Locale setup for non-shells

2017-05-24 Thread Nikolai Kondrashov
On 05/23/2017 11:42 PM, Lennart Poettering wrote: On Mon, 22.05.17 19:36, Nikolai Kondrashov (nikolai.kondras...@redhat.com) wrote: I'm talking about logins on console now, so I assume the service in question, technically, is systemd-logind. However, I found out that it's working OK

Re: [systemd-devel] Locale setup for non-shells

2017-05-22 Thread Nikolai Kondrashov
On 05/22/2017 04:46 PM, Lennart Poettering wrote: On Mon, 22.05.17 14:11, Nikolai Kondrashov (nikolai.kondras...@redhat.com) wrote: 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. Which services

Re: Locale setup for non-shells

2017-05-22 Thread Nikolai Kondrashov
systemd can help here? Thank you. Nick On 04/04/2017 06:06 PM, Nikolai Kondrashov wrote: Hi everyone, At the moment users logging into Fedora on a text terminal (console, SSH, etc.) get their locale environment variables (LANG, LC_ALL, etc.) set up by the shell they use. I.e. the shell

Re: Locale setup for non-shells

2017-05-22 Thread Nikolai Kondrashov
On 05/22/2017 01:30 PM, Tomas Mraz wrote: On Mon, 2017-05-22 at 12:46 +0300, Nikolai Kondrashov wrote: Do you think the below could be done, from PoV of PAM/authconfig? I do not have any problem with this if the locale.conf file is really in format that is accepted by pam_env. It seems

Re: Locale setup for non-shells

2017-05-22 Thread Nikolai Kondrashov
Hi Tomas, Do you think the below could be done, from PoV of PAM/authconfig? On 04/04/2017 06:06 PM, Nikolai Kondrashov wrote: At the moment users logging into Fedora on a text terminal (console, SSH, etc.) get their locale environment variables (LANG, LC_ALL, etc.) set up by the shell they use

Locale setup for non-shells

2017-04-04 Thread Nikolai Kondrashov
Hi everyone, At the moment users logging into Fedora on a text terminal (console, SSH, etc.) get their locale environment variables (LANG, LC_ALL, etc.) set up by the shell they use. I.e. the shell ultimately sources the /etc/locale.conf file. This works fine in most cases. However, if the user

Re: Mass issue: /usr/bin/env dependency

2017-03-29 Thread Nikolai Kondrashov
On 03/29/2017 04:52 PM, Tomasz Kloczko wrote: > On Wed, 2017-03-29 at 12:26 +0000, Nikolai Kondrashov wrote: >> I would say using env in the shebang line is useful. Particularly for >> portability. As a developer, I wouldn't like removing it from my programs. > > Portab

Re: Mass issue: /usr/bin/env dependency

2017-03-29 Thread Nikolai Kondrashov
On 03/29/2017 04:16 PM, Ralf Corsepius wrote: > On 03/29/2017 02:26 PM, Nikolai Kondrashov wrote: >> I would say using env in the shebang line is useful. Particularly for >> portability. As a developer, I wouldn't like removing it from my programs. > > FPC repeated discusse

Re: Mass issue: /usr/bin/env dependency

2017-03-29 Thread Nikolai Kondrashov
I would say using env in the shebang line is useful. Particularly for portability. As a developer, I wouldn't like removing it from my programs. Moreover, if your PATH is compromised, you're most likely screwed. I understand, that env use in scripts makes is inconvenient in some cases, but I