Comment 11 for bug 138217

Has this bug been fixed yet? I am getting killed here with my logs being filled up by NetworkManager. How do I prevent it from starting? I tried to grep for it in /etc/init.d but none of the scripts contain it. I killed it manually, and of course, I lost connection. Upon restarting networking, I got connection back without NetworkManager processes running:

=> ps -ef | grep NetworkManager
root 5958 1 0 08:47 ? 00:00:51 /usr/sbin/NetworkManager --pid-file /var/run/NetworkManager/NetworkManager.pid
root 5974 1 0 08:47 ? 00:00:29 /usr/sbin/NetworkManagerDispatcher --pid-file /var/run/NetworkManager/NetworkManagerDispatcher.pid
bmynars 29539 26348 0 10:47 pts/1 00:00:00 grep NetworkManager
root 29567 5974 0 10:47 ? 00:00:00 sh -c /etc/NetworkManager/dispatcher.d/01ifupdown eth0 pre-up

So, if I do not need it, why does it start in the first place?

It fills up syslog and daemon.log files (very small sample only):

Apr 27 10:48:30 tux-229 NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Apr 27 10:48:30 tux-229 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Apr 27 10:48:30 tux-229 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Apr 27 10:48:30 tux-229 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Apr 27 10:48:30 tux-229 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Apr 27 10:48:30 tux-229 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Apr 27 10:48:30 tux-229 NetworkManager: <WARN> nm_dhcp_manager_begin_transaction(): dhcdbd not running!
Apr 27 10:48:30 tux-229 NetworkManager: <info> Activation (eth0) failure scheduled...
Apr 27 10:48:30 tux-229 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.