From 68df1229896c799f923263e7437a5ef6096bca1a Mon Sep 17 00:00:00 2001
From: Javier Viguera <javier.viguera@digi.com>
Date: Wed, 19 Apr 2017 14:17:03 +0200
Subject: [PATCH] modemmanager: enable log file

Instead of redirecting the MM logging to '/dev/null' use a file, so we
can see what's going on in case of failure.

Signed-off-by: Javier Viguera <javier.viguera@digi.com>
---
 .../modemmanager/modemmanager/cellularifupdown                  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-digi-dey/recipes-connectivity/modemmanager/modemmanager/cellularifupdown b/meta-digi-dey/recipes-connectivity/modemmanager/modemmanager/cellularifupdown
index 88e2072aa..f38082719 100644
--- a/meta-digi-dey/recipes-connectivity/modemmanager/modemmanager/cellularifupdown
+++ b/meta-digi-dey/recipes-connectivity/modemmanager/modemmanager/cellularifupdown
@@ -8,7 +8,7 @@ POLLING_WAIT=5
 
 background_connect() {
         # Ensure ModemManager is running
-        killall -0 ModemManager 2>/dev/null || ModemManager --log-file=/dev/null &
+        killall -0 ModemManager 2>/dev/null || ModemManager --log-file=/var/log/modemmanager.log &
 
         # Wait for modem detection
         while [ "${RETRIES}" -gt "0" ]; do