Re: tmpfs
Boris via leaf-user <[email protected]> Tue, 26 Nov 2024 00:00:32 +0100
| Newsgroups | gmane.linux.leaf.user |
|---|---|
| Message-ID | <[email protected]> |
Hej KP, Am 25.11.24 um 17:28 schrieb KP.Kirchdoerfer: > Hi, > > first of all, logging is complicated, and maybe even a mess. Historically grown > from different log routines and programs, as well as some packages providing > their own mechanisms and so son - I agree this needs more consolidation and > explanation/documentation. > I remember the search for good documentation and the failure because of too little knowledge about this part of the game (wifi technology). Logging did not take much my attention. I took it for granted. hostapd was logging to /var/log/hostapd.log an I felt fine with that. > Am Samstag, 23. November 2024, 23:47:10 CET schrieb Erich Titl: >> Depending how hostapd is logging. As said before it can log to syslog or >> to stdout (when not running in background). >> >> # >> # Levels (minimum value for logged events): >> # 0 = verbose debugging >> # 1 = debugging >> # 2 = informational messages >> # 3 = notification >> # 4 = warning >> # >> logger_syslog=3 >> logger_syslog_level=2 >> logger_stdout=0 >> logger_stdout_level=4 >> >> You set logger_syslog to -1, no idea what this is. It probably does >> nothing. Now I don't know where you got these values from. You should >> use one of the defined methods and levels for syslog to do something >> reasonable. And no, DAEMON should be rsyslog. > > These values are from hostapd.conf. > > The value for logger_syslog is documented as follows: > # 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 > > The value logger_syslog_level is linked in rsyslog.conf to the logfile you > choose for this log_level. > > here hostapd.conf: > > #Levels (minimum value for logged events): > # 0 = verbose debugging > # 1 = debugging > # 2 = informational messages > # 3 = notification > and so on > > and in rsyslog.conf: > > # Some "catch-all" log files. > # > *.=debug;\ > auth,authpriv.none;\ > news.none;mail.none -/var/log/debug > *.=info;*.=notice;*.=warn;\ > auth,authpriv.none;\ > cron,daemon.none;\ > mail,news.none -/var/log/syslog > > Here are my entries for hostapd > logger_syslog=-1 > logger_syslog_level=2 > Fine. So I kicked (commented) off the two lines #logger_stdout=-1 #logger_stdout_level=2 and remained the rest like on your box. ... and realized a change in behaviour: While /var/log/hostapd was size 0 -rw-r----- 1 root adm 0 Nov 22 06:42 hostapd.log , it is now increasing slowly as expected. Thanks so far. > Meaning > > - log all modules > - log with level "info" > > and looking into rsyslog "info" goes to /var/log/syslog cannot confirm that. Boris ------------------------------------------------------------------------ leaf-user mailing list: [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/