Le 12/11/2010 14:22, Timothy Murphy a écrit :
> Over half the entries in my /var/log/messages (under Fedora-14/KDE)
> are NetworkManager messages.
> I've never found these of the slightest use on the fairly rare occasions
> when NM fails.
>
> Is there any way of cutting down on these communication
Over half the entries in my /var/log/messages (under Fedora-14/KDE)
are NetworkManager messages.
I've never found these of the slightest use on the fairly rare occasions
when NM fails.
Is there any way of cutting down on these communications?
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
Hello!
Just drop drop a dbus stuff. It seems is unused anywhere. And in any
case it cause segfault if dbus_g_bus_get() returns NULL.
--
WBR, Mikhail Efremov
>From feb40da3359f8e88d509f49d65a835ee7291066d Mon Sep 17 00:00:00 2001
From: Mikhail Efremov
Date: Mon, 8 Nov 2010 17:16:18 +0300
Subject
> Could you install debug packages and run NetworkManager from within gdb to
> obtain better backtrace?
>
> # gdb NetworkManager
> (gdb) run --no-daemon
>
> and when it crashes do
> (gdb) t a a bt
>
> Jirka
>
I run modprobe e1000e and this is gdb output:
NetworkManager[4998]: (eth0): carrier is
Hello!
Since NM does not stop dhcp client when it exits, there may persist an
old instance of dhcp client during NM start again and it is not a child
of the current process. So we need to wait until it is actually exited,
otherwise a race condition may occurs, as I noticed in case dhcpcd
4.x.x (th
