After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 724657 - Scripts run by NM dispatcher don't have PATH environment variable set
Scripts run by NM dispatcher don't have PATH environment variable set
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: general
0.9.8
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-02-18 15:41 UTC by Tomas Hozza
Modified: 2014-04-18 15:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Tomas Hozza 2014-02-18 15:41:33 UTC 
Scripts run by NM dispatcher don't have the PATH environment variable set,
therefore they have to use full paths to binaries or set the PATH variable
by themself.

This is causing problems if some script is used on various distributions on
which paths to the same binary may differ. It would make things much easier
if scripts run by NM dispatcher had the PATH set accordingly to the system.
Comment 1 Pavel Simerda 2014-02-19 07:30:39 UTC 
Was curious how systemd does that and learned that systemd session daemons pass the environment they're started in and the systemd system daemon passes an environment it builds itself up with a value of {/,/usr/,/usr/local/}{bin,sbin}.

With NetworkManager, we can use either way and they are in fact equivalent on systems using systemd, as NetworkManager itself is being run from systemd with the static list of paths.
Comment 2 Dan Winship 2014-04-18 15:45:46 UTC 
fixed in git master