Bugzilla – Bug 147748
NetworkManager debug verbosity
Last modified: 2006-02-15 18:07:03 UTC
As per bug #147648, let's start to discuss what kind of debug messages NM should log? I'v CCed Marcus, as this might have some connection to security policies (because AFAIK NM logs some passphrases to /var/log/messages, e.g.). While a lof a messages are helping to debug stuff, they aren't really needed in most cases, where the users just uses NM. Any thoughts / suggestions how to handle this?
Good idea to discuss this. A few thoughts of my own: a) Should definitely not log passphrases. I will look into that. b) We can consider logging less, e.g. only warnings or and errors. But... c) We need some way to re-enable debug/info logging for e.g. developers and debugging.
Submitted updated NM today (0.5.1cvs20060203) that does not print the passphrases. So (a) is now taken care of.
NM no longer outputs security information. Is there still an issue with the daemon's verbosity? What is the concensus on what it should do? Marking NEEDINFO: Let's have a dialogue or consider the issue closed.
If we can not provide some --enable-debug switch in time, I'd at least log to a specific log file rather than logging to /var/log/messages.
I'm very much in favor of Timo's proposal -- besides that I'd consider this issue fixed. Oh, maybe we could change the debug output in some places to "stage x of y" instead of "stage x", that might help users that don't know much about NM yet to find out if they are stuck in, e.g. stage 2...
I am happy with both proposals. We log to /var/log/messages because that is where syslog puts us. How do we change that? Add an entry to /etc/syslog-ng/syslog-ng.conf?
I'll attach a patch against syslog-ng.conf.in. SuSEconfig should then set up syslog-ng.conf correctly.
Created attachment 68463 [details] add rule for NetworkManager to syslog-ng.conf.in
Marius, can you please put this rule for NetworkManager into syslog-ng?
I'll add it and provide the logrotation config as well, except Andreas/Gerald has objections against it...
Go ahead.
Submitted to STABLE.
Thanks, Marius!
why does this whole nm stuff have to be so ugly with all this mixed-caps names. Can't we just name the logfile /var/log/networkmanager?
Fine with me. My intention was to have the logfile named as the binary which is causing the logs ;-)
fix the name of the binary ;-)
Marking as resolved.