Hi,
On Tue, Jul 28, 2020 at 08:08:40 -0400, Sam Hartman wrote:
> >>>>> "Petter" == Petter Reinholdtsen <p...@hungry.com> writes:
>
> Petter> In Debian Edu, /etc/environment is used to set the required
> Petter> HTTP proxy globally. It would be nice if it actually took
> Petter> effect for all services. :)
That's my current problem: PROXYs not being consistently
set in some services. (like sudo -i)
> I'd argue that this should be set in the systemd unit for the service
> for a service that does not traditionally use sessions.
> Also, I believe there is a way to get systemd to inject environment
> variables into init's environment, so they are inherited until the
> environment is cleared.
> I'd generally agree that applications should either preserve their
> environment, or use pam_env.
So we should go around and ask every service, that could
need a proxy to properly read /etc/environment either via
pam_env or via systemd's EnvirontFile (or whatever the name
was)?
I have another question:
Can you imagine a (sane) setting in /etc/environment
breaking a (sane) application, when we add pam_env to
common-session*?
Settings, that are not for the system as a whole, should be
in another file. For example the locale is in
/etc/default/locale, and it is sensible to only load it for
local (interactive) users. So we have a clear set of
applications, that we need to modify.
But for /etc/environment I can't imagine any application,
that should not read it.
Greetings
Elrond
