Re: Modem-manager logging levels

>>> How do I get NM to start modem-manager with "--log-level=WARN"?
>> You'll need to avoid having NM do the dbus-activated start. You can
>> avoid this by moving the modem-manager binary from
>> /usr/sbin/modem-manager to another location, like /modem-manager. Once
>> you do that, you'll need to launch the program yourself, and you can
>> then pass whatever log level you want with --log-level.
>> If you just want to change the log level, another option if you have a
>> recent enough MM is to use the SetLogging method in the ModemManager
>> DBus interface, like:
>> $> sudo dbus-send --system \
>>                   --dest=org.freedesktop.ModemManager \
>>                   --print-reply \
>>                   /org/freedesktop/ModemManager \
>>                   org.freedesktop.ModemManager.SetLogging \
>>                   string:Warn
>> Thanks, I had found the dbus command above but it does not seem to persist
>> after a suspend/resume of my laptop. MM seems to get restarted. Maybe NM
>> could be changed to start MM with the same log-level it has set in its
>> .conf file? 

ModemManager should not get restarted in the first place. Are you able
to reproduce the issue and provide debug logs and ideally a stacktrace?


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]