diff options
| author | Thomas Haller <thaller@redhat.com> | 2018-06-18 13:08:16 +0200 |
|---|---|---|
| committer | Thomas Haller <thaller@redhat.com> | 2018-06-18 14:19:16 +0200 |
| commit | 2800232bbf6f44e6776bd18286d5d51fdf70392b (patch) | |
| tree | 9f8a57d3b3dc303956f4a71d30f75744a4569c04 /NEWS | |
| parent | f8dfc436b13f7a2f15e1f1a81086ba4b38e90ee4 (diff) | |
| download | NetworkManager-2800232bbf6f44e6776bd18286d5d51fdf70392b.tar.gz | |
dispatcher: add NM_DISPATCHER_ACTION environment variable
Previously, the action was only passed as the first command line
argument to the dispatcher scripts. Now, also set it via the
"$NM_DISPATCHER_ACTION" environment variable.
The main purpose is to have a particular, nm-dispatcher specific
variable that is always set inside the dispatcher scripts.
For example, imagine you have a script that can be either called by
dispatcher or some other means (manually, or spawned via
/etc/NetworkManager/dispatcher.d/11-dhclient). Then it might make
sense to differenciate from inside the script whether you are called
by nm-dispatcher. But previously, there was no specific environment
variable that was always set inside the dispatcher event. For example,
with the "hostname" action there are no other environment variables.
Now (with version 1.12), you can check for `test -n "$NM_DISPATCHER_ACTION"`.
(cherry picked from commit ce9619047c5daac9a006d16d07453d50e0520e71)
Diffstat (limited to 'NEWS')
| -rw-r--r-- | NEWS | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -47,6 +47,7 @@ Notable changes include: The following features were backported to 1.10.x releases from 1.10.0 to 1.10.10 are also present in NetworkManager-1.12: +* Set NM_DISPATCHER_ACTION environment variable in dispatcher scripts. * Fix crash during reapply of connection settings * Fix connectivity timeout handling (bgo #794464), * Retry activating devices when the parent becomes managed (rh #1553595), |