Re: tmpfs

Hej Erich,

Am 23.11.24 um 23:47 schrieb Erich Titl:
> Hi Boris
> 
> Am 23.11.2024 um 23:21 schrieb Boris:

[snip]

>> OK, here is the content of /etc/logrotate.d/ntp
>>
>> LOGS_WEEKLY="ntpd"
>> LOGSIZE=4096
>> DAEMON=rsyslog
>> METHOD=restart
>> COMPRESS_ALL=1
> 
> Now as ntpd does its own logging the DAEMON looks wrong. it should be ntp.

OK, set to ntp. Let's see....

> 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.
> 
> So it looks like some of your files were modified, possibly out of 
> focus. This of course could make logrotate choke.

My hostapd configuration is a collection from various sources. A few 
years ago I installed a 5GHz card and had great difficulty getting it to 
work for weeks. After I succeeded, I never touched the configuration again.
In fact, -1 turns off logging to syslog _and_ stdout, as I have now 
read. The question remains, why hostapd logs at all?

I will have to deal with this configuration again.

Boris


------------------------------------------------------------------------
leaf-user mailing list: [email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/