On Sat, Jan 31, 2009 at 07:12:46PM -, Endolith wrote:
> By the way, the author of wpa_supplicant has confirmed that this is a
> problem with Network Manager. wpa_supplicant sends messages about state
> changes over D-Bus, and then Network Manager generates the logs based on
> those messages (n
By the way, the author of wpa_supplicant has confirmed that this is a
problem with Network Manager. wpa_supplicant sends messages about state
changes over D-Bus, and then Network Manager generates the logs based on
those messages (nm-device-wifi.c ), though he feels there is no reason
for NM to lo
On Thu, Jan 29, 2009 at 01:42:01AM -, Endolith wrote:
> Note that wpasupplicant has quiet switches as well as verbose switches.
> Calling it with the quiet switch is probably the solution, so this bug
> should not be closed.
>
If you continue to do that I will have no other chance but ignore
Note that wpasupplicant has quiet switches as well as verbose switches.
Calling it with the quiet switch is probably the solution, so this bug
should not be closed.
--
Executes wpa_supplicant in too verbose mode
https://bugs.launchpad.net/bugs/51784
You received this bug notification because you
On Tue, Jan 20, 2009 at 08:11:36PM -, Tormod Volden wrote:
> > In the normal course of things people generally don't tail their own
> syslog, so the impact is fairly low
>
> Unnecessary logging is not good on laptops which try to save energy and
> spin down hard drivers, for instance.
>
Plea
On Tue, Jan 20, 2009 at 03:45:45PM -, Chris Jones wrote:
> wpa_supplicant in Intrepid is *not* being started with -d or -dd, so
> this bug is fixed.
>
> There is a separate issue with wpa_supplicant being arguably too noisy
> in its normal operation. That should be filed and fixed separately.
> In the normal course of things people generally don't tail their own
syslog, so the impact is fairly low
Unnecessary logging is not good on laptops which try to save energy and
spin down hard drivers, for instance.
--
Executes wpa_supplicant in too verbose mode
https://bugs.launchpad.net/bugs/
wpa_supplicant in Intrepid is *not* being started with -d or -dd, so
this bug is fixed.
There is a separate issue with wpa_supplicant being arguably too noisy
in its normal operation. That should be filed and fixed separately.
AFAIK it's nothing to do with NetworkManager, it's just wpa_supplicant
"There is a separate issue with wpa_supplicant being arguably too noisy
in its normal operation."
Got it. Thanks.
--
Executes wpa_supplicant in too verbose mode
https://bugs.launchpad.net/bugs/51784
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
You can run 'ps -ef | grep wpa_ | grep -v grep' to get the command line
used by NM to start wpa_supplicant.
But the point is that while you may not care where the messages come
from, which I understand perfectly, but *we* care for clarity's sake.
Open a new report, because if your problem is still
There's some kind of miscommunication here.
In Ubuntu Intrepid, does NetworkManager still start wpa_supplicant with either
-d or -dd?
If it still does, then why is this bug marked Fixed?
If it doesn't, then why is it still logging "supplicant connection state
change" messages several times per m
** Changed in: network-manager
Status: New => Fix Released
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Fix Released
--
Executes wpa_supplicant in too verbose mode
https://bugs.launchpad.net/bugs/51784
You received this bug notification because you are a member of U
What Alexander means is that the present report is about NetworkManager
starting wpa_supplicant with the -d option, which makes it print debug
messages. What you complain about is that wpa_supplicant considers this
log message as 'notice' then it should be 'debug'. Those problems are
tightly relate
This bug is about the log messages being too verbose, which is still the
problem and should not be marked closed. I believe this is the same
problem as the bug that I filed Bug #294190. If not, please separate
them.
Can someone please explain why these messages are being produced in the
first pl
On Thu, Jan 08, 2009 at 02:44:14PM -, Endolith wrote:
> Why is that a different bug? This one is about verbose logging.
>
Because this one is closed and was about debug output ... not messages
that should be debug messages and are not.
- Alexander
--
Executes wpa_supplicant in too verbos
Why is that a different bug? This one is about verbose logging.
--
Executes wpa_supplicant in too verbose mode
https://bugs.launchpad.net/bugs/51784
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
On Tue, Jan 06, 2009 at 05:30:24PM -, Endolith wrote:
> And the priority is still "notice", not "debug".
>
Yes, thats a different bug then this one (this was about debug
logging). Plesae file a new bug. Thanks!
- Alexander
--
Executes wpa_supplicant in too verbose mode
https://bugs.launch
And the priority is still "notice", not "debug".
--
Executes wpa_supplicant in too verbose mode
https://bugs.launchpad.net/bugs/51784
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
Why would it be sent to its own log anyway? I don't see anyone saying
that this information is actually useful for anything. Why is this
being logged in the first place?
--
Executes wpa_supplicant in too verbose mode
https://bugs.launchpad.net/bugs/51784
You received this bug notification becau
> Where do you see this verbosity?
> tail /var/log/syslog
Jan 6 12:12:13 inspiron NetworkManager: (eth1): supplicant connection
state change: 5 -> 6
Jan 6 12:12:13 inspiron NetworkManager: (eth1): supplicant connection
state change: 6 -> 7
Jan 6 12:14:12 inspiron NetworkManager: (eth1
On Tue, Jan 06, 2009 at 01:47:57AM -, Endolith wrote:
> This is still not fixed. Can it be re-opened?
Where do you see this verbosity? Since intrepid most stuff goes to its
own log, so it shouldnt clutter syslog anymore.
- Alexander
--
Executes wpa_supplicant in too verbose mode
https://b
Since the open bug 294190 was marked as a duplicate of this one, I
reopen it.
** Changed in: network-manager (Ubuntu)
Status: Fix Released => Confirmed
--
Executes wpa_supplicant in too verbose mode
https://bugs.launchpad.net/bugs/51784
You received this bug notification because you are a
This is still not fixed. Can it be re-opened?
** Also affects: network-manager
Importance: Undecided
Status: New
--
Executes wpa_supplicant in too verbose mode
https://bugs.launchpad.net/bugs/51784
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
NetworkManager is certainly still spamming syslog, and the priority of
the spam is "notice", not "debug". Is there something wrong with my
configuration (Hardy) or has it regressed since this bug was closed?
--
Executes wpa_supplicant in too verbose mode
https://bugs.launchpad.net/bugs/51784
You
** Changed in: network-manager (Debian)
Status: New => Fix Released
--
Executes wpa_supplicant in too verbose mode
https://bugs.launchpad.net/bugs/51784
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
0.6.5 doesn't do this anymore. Closing.
** Changed in: network-manager (Ubuntu)
Status: In Progress => Fix Released
--
Executes wpa_supplicant in too verbose mode
https://bugs.launchpad.net/bugs/51784
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Alexander Sack <[EMAIL PROTECTED]> writes:
> i somehow must be blind ... can you tell me where those log messages end
> up for you?
grep for them in /var/log if you're running NetworkManager. They're
pretty unmistakable.
Perry
--
Executes wpa_supplicant in too verbose mode
https://bugs.launchp
i somehow must be blind ... can you tell me where those log messages end
up for you?
--
Executes wpa_supplicant in too verbose mode
https://bugs.launchpad.net/bugs/51784
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bu
Alexander Sack <[EMAIL PROTECTED]> writes:
> On Fri, May 25, 2007 at 07:59:26AM -, Stefan Björk wrote:
>> Is changing syslog facility/level an redirecting all the output to
>> /var/log/debug (or similar) an alternative?
>
> I don't think that all output should go to debug ... I agree that we
>
On Fri, May 25, 2007 at 07:59:26AM -, Stefan Björk wrote:
> Is changing syslog facility/level an redirecting all the output to
> /var/log/debug (or similar) an alternative?
>
I don't think that all output should go to debug ... I agree that we
should have a less verbose level of output. The q
Is changing syslog facility/level an redirecting all the output to
/var/log/debug (or similar) an alternative?
--
Executes wpa_supplicant in too verbose mode
https://bugs.launchpad.net/bugs/51784
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
Alexander Sack <[EMAIL PROTECTED]> writes:
> So how do we want this fixed? is -d ok or too much output as well?
-d is too much in ordinary circumstances.
I think it would be best if it was configurable, say with a command
line flag to network manager or a config file change. That way, it
would b
So how do we want this fixed? is -d ok or too much output as well?
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Alexander Sack
Status: Confirmed => In Progress
--
Executes wpa_supplicant in too verbose mode
https://bugs.launchpad.net/bugs/51784
You received this
We should really fix this for Gutsy.
** Changed in: network-manager (Ubuntu)
Importance: Wishlist => Medium
Target: None => ubuntu-7.10
--
Executes wpa_supplicant in too verbose mode
https://bugs.launchpad.net/bugs/51784
You received this bug notification because you are a member of Ub
The claim that the output is needed for support is specious. The
messages in question are not very important. However, the messages
filling the log *is* a very serious issue.
The entire method that NetworkManager is using to execute
wpa_supplicant, to whit, hard coding options in an array in an ob
35 matches
Mail list logo
