summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThomas Haller <thaller@redhat.com>2015-04-17 15:46:17 +0200
committerThomas Haller <thaller@redhat.com>2015-05-13 18:44:07 +0200
commit8da0a8104a56b795eba962420f7836c5bb3f7a19 (patch)
tree825566b53c5a5abf9008ae7e9c3a0d0bd3db1ccd
parent3d17c73576d878fa724554822fc4736cfcc28b4e (diff)
downloadNetworkManager-8da0a8104a56b795eba962420f7836c5bb3f7a19.tar.gz
device/logging: log connection UUID when activating connection
It is often hard to understand whether we activate an assumed connection. Only the UUID is unique. (cherry picked from commit 9983e4eff5b07ed217cf60785039dfeb9fbbfd19)
-rw-r--r--src/devices/nm-device.c5
1 files changed, 3 insertions, 2 deletions
diff --git a/src/devices/nm-device.c b/src/devices/nm-device.c
index 4d964c82b3..d23a49178a 100644
--- a/src/devices/nm-device.c
+++ b/src/devices/nm-device.c
@@ -5763,8 +5763,9 @@ _device_activate (NMDevice *self, NMActRequest *req)
connection = nm_act_request_get_connection (req);
g_assert (connection);
- _LOGI (LOGD_DEVICE, "Activation: starting connection '%s'",
- nm_connection_get_id (connection));
+ _LOGI (LOGD_DEVICE, "Activation: starting connection '%s' (%s)",
+ nm_connection_get_id (connection),
+ nm_connection_get_uuid (connection));
delete_on_deactivate_unschedule (self);