Your message dated Wed, 23 May 2012 02:33:24 +0200
with message-id <[email protected]>
and subject line Re: hostapd: does not report errors
has caused the Debian Bug report #568181,
regarding hostapd: does not report errors
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
568181: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568181
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: hostapd
Version: 1:0.5.10-1
Severity: important
When running starting hostapd fails the hostapd error is not logged anywhere.
It does not appear on the terminal where the start is attempted not is it
logged in /var/log/daemon.log nor in any other log file I searched.
Running hostapd manually with the parameters used in the init script shows the
error.
-- System Information:
Debian Release: 5.0.3
APT prefers stable
APT policy: (800, 'stable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages hostapd depends on:
ii libc6 2.10.2-2 GNU C Library: Shared libraries
ii libssl0.9.8 0.9.8k-8 SSL shared libraries
ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip
hostapd recommends no packages.
hostapd suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Package: hostapd
Version: 0.7.3-1
Hi
I think this got fixed in the 0.7 branch, at least it can be configured
from your hostapd.conf now:
# hostapd event logger configuration
#
# Two output method: syslog and stdout (only usable if not forking to
# background).
#
# Module bitfield (ORed bitfield of modules that will be logged; -1 = all
# modules):
# bit 0 (1) = IEEE 802.11
# bit 1 (2) = IEEE 802.1X
# bit 2 (4) = RADIUS
# bit 3 (8) = WPA
# bit 4 (16) = driver interface
# bit 5 (32) = IAPP
# bit 6 (64) = MLME
#
# Levels (minimum value for logged events):
# 0 = verbose debugging
# 1 = debugging
# 2 = informational messages
# 3 = notification
# 4 = warning
#
logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2
…which does log to syslog.
Regards
Stefan Lippers-Hollmann
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
