The net-misc/networkmanager-0.6.6 prints a lot of debug message to current active console tty. When I started the daemon and then switched to tty2 (already loged in), A message "NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface eth0" poped out in the tty. I then switched to tty1, A message "NetworkManager: <info> DHCP daemon state is now 2 (bound) for interface eth0" poped out where the cursur was. After a while, I got my tty1 filled with the NetworkManager infos. However, when I then switched to tty2, there was only the "now 1" message. It seems that NetworkManager tends to prints its current log message to the current active console tty. Reproducible: Always The message is printed by a call nm_info in nm_device.c. The nm_info is actually g_message(...). So it is really strange that the g_message call outputs its message to the current tty.
Thanks to Dan Williams' help, Just start the syslog daemon and everything works just fine. So it is strage that the NetworkManager script does not require syslog to start while it uses the functionality of syslog. We may fix this by adding a dependency for /etc/init.d/NetworkManager. see http://bugzilla.gnome.org/show_bug.cgi?id=573857 for more information.
Well this can be argued if an app's init script should really depend on syslog. I remember that I found some services on one of my machines which show the same behavior and I didn't consider their init-scripts to be buggy. I'd say this is up to a machine's admin to resolve such kind of "inconvenience". Anyway, reassigning to/CCing maintainers as they may have a different opinion about this.
The NetworkManager works without syslog, as you described. Depending on the init script would mean NM requires a logger to run, and that is not the case. If you don't want to see every second service's messages on your console, start syslog as described in the handbook.
(In reply to comment #3) > The NetworkManager works without syslog, as you described. Depending on the > init script would mean NM requires a logger to run, and that is not the case. > If you don't want to see every second service's messages on your console, start > syslog as described in the handbook. > Thanks. So this may not be considered a bug actually. It only causes inconvenience.
