Bug 147748

Summary: NetworkManager debug verbosity
Product: [openSUSE] SUSE Linux 10.1 Reporter: Christoph Thiel <cthiel>
Component: NetworkAssignee: Robert Love <rml>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Enhancement    
Priority: P5 - None CC: gp, meissner, suse-beta
Version: Beta 3   
Target Milestone: Beta 5   
Hardware: Other   
OS: SuSE Linux 10.1   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: add rule for NetworkManager to syslog-ng.conf.in

Description Christoph Thiel 2006-02-02 18:06:55 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?
Comment 1 Robert Love 2006-02-02 18:34:56 UTC
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.
Comment 2 Robert Love 2006-02-03 20:18:19 UTC
Submitted updated NM today (0.5.1cvs20060203) that does not print the passphrases.  So (a) is now taken care of.
Comment 3 Robert Love 2006-02-14 20:59:26 UTC
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.
Comment 4 Timo Hoenig 2006-02-14 21:06:13 UTC
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.
Comment 5 Christoph Thiel 2006-02-14 22:10:06 UTC
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...
Comment 8 Robert Love 2006-02-14 22:21:03 UTC
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?
Comment 9 Timo Hoenig 2006-02-14 22:39:59 UTC
I'll attach a patch against syslog-ng.conf.in.  SuSEconfig should then set up syslog-ng.conf correctly.
Comment 10 Timo Hoenig 2006-02-14 22:42:02 UTC
Created attachment 68463 [details]
add rule for NetworkManager to syslog-ng.conf.in
Comment 11 Timo Hoenig 2006-02-14 22:43:24 UTC
Marius, can you please put this rule for NetworkManager into syslog-ng?
Comment 12 Marius Tomaschewski 2006-02-15 10:50:59 UTC
I'll add it and provide the logrotation config as well,
except Andreas/Gerald has objections against it...
Comment 13 Andreas Jaeger 2006-02-15 12:18:38 UTC
Go ahead.
Comment 14 Marius Tomaschewski 2006-02-15 13:12:46 UTC
Submitted to STABLE.
Comment 15 Timo Hoenig 2006-02-15 13:20:44 UTC
Thanks, Marius!
Comment 16 Forgotten User ZhJd0F0L3x 2006-02-15 15:04:09 UTC
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?
Comment 17 Timo Hoenig 2006-02-15 15:15:33 UTC
Fine with me.  My intention was to have the logfile named as the binary which is causing the logs ;-)
Comment 18 Forgotten User ZhJd0F0L3x 2006-02-15 15:34:06 UTC
fix the name of the binary ;-)
Comment 19 Robert Love 2006-02-15 18:07:03 UTC
Marking as resolved.