> Not sure. Maybe raise this question upstream.
https://github.com/systemd/systemd/issues/6414
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
Am 21.07.2017 um 01:01 schrieb Stefan Tatschner:
>> The PATH you have above is not hard-coded in systemd afaics.
>> To me this looks like PATH is set somewhere outside of systemd and then
>> pushed into the systemctl --user environment.
>
> Any idea how I can find out which component is
> The PATH you have above is not hard-coded in systemd afaics.
> To me this looks like PATH is set somewhere outside of systemd and then
> pushed into the systemctl --user environment.
Any idea how I can find out which component is overwriting PATH?
(sry, I did not hit reply all in the first
Am 20.07.2017 um 23:24 schrieb Stefan Tatschner:
> Subject: systemd: Setting PATH with environment.d does not work
> Package: systemd
> Version: 234-1
> Severity: normal
>
> Dear Maintainer,
>
> Setting the $PATH variable with systemd's environment.d feature does not work
> as expected. I have
