After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 573857 - networkmanager outputs a lot of messages to current active console tty
networkmanager outputs a lot of messages to current active console tty
Status: RESOLVED NOTGNOME
Product: NetworkManager
Classification: Platform
Component: general
0.6.6
Other All
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2009-03-03 03:24 UTC by Yang Zhang
Modified: 2009-03-05 11:34 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Yang Zhang 2009-03-03 03:24:58 UTC
Please describe the problem:
The networkmanager daemon 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. 


Steps to reproduce:
1. Just start NetworkManager as root in a console terminal, direct all its output to /dev/null.
 


Actual results:
The current console is then filled with "NetworkManager: <info> ..." messages. When switch to other consoles, the messages then goes there.

Expected results:
The messages should go to some where else, not to the current colsole.

Does this happen every time?
Every time.

Other information:
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.
Comment 1 Dan Williams 2009-03-03 21:33:46 UTC
The will go to syslog unless you've specified --no-daemon.  I'd suggest adding some syslog rules to direct NetworkManager output to /var/log/NetworkManager.log or something like that instead of the console.
Comment 2 Yang Zhang 2009-03-04 03:02:55 UTC
Thanks for your help. After starting the syslog-ng daemon, everything works just fine. Maybe this is a gentoo-related bug. The NetworkManager does not require syslog to start.
Comment 3 Dan Williams 2009-03-05 11:34:00 UTC
Yes, sounds like a packaging bug where the gentoo package isn't starting syslog before NM.