Re: tmpfs
Erich Titl <[email protected]> Mon, 2 Dec 2024 17:28:32 +0100
| Newsgroups | gmane.linux.leaf.user |
|---|---|
| Message-ID | <[email protected]> |
Hi Boris Am 02.12.2024 um 16:52 schrieb Boris via leaf-user: > Am 02.12.24 um 16:45 schrieb Boris via leaf-user: >> Am 02.12.24 um 16:36 schrieb Boris via leaf-user: >>> 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. >>> >>> Hej everybody, >>> hej Erich and KP, >>> >>> some days are gone and I can put one on top. >>> >>> After commenting the log-Parameters 'stdout' in hostapd.conf, >>> behaviour seemed much better. >>> >>> Today I wanted to monitor a new dhcp-client with tail -f /var/log/ >>> dameon.log an found: >>> >>> # tail -f /var/log/daemon.log >> [snip] >>> b8:27:eb:0f:56:dc >>> Dec 1 05:44:44 192 dnsmasq[2808]: overflow: 2248 log entries lost >>> Dec 1 05:44:44 192 dnsmasq-dhcp[2808]: DHCPACK(eth1) 192.168.23.196 >>> b8:27:eb:0f:56:dc nl-raspi2-koje >> >> [snip] >> >>> root 64.0M 42.6M 21.4M 67% / >>> >>> That's still the old game.... >>> >> >> To get daemon.log working again, I restarted dnsmasq - with no success. >> So I restarted rsyslog - with a surprising insight: >> >> # /etc/init.d/rsyslog restart >> Stopping rsyslog daemon: FAIL >> Starting rsyslog daemon: OK Again rsyslog appears to be stopped or the stop command does something weird. >> >> daemon.log active again, > > In the reactivated daemon.log I found this: > > Dec 2 15:39:36 192 dnsmasq[10951]: using nameserver 213.178.70.1#53 > Dec 2 15:39:36 192 dnsmasq[10951]: using nameserver 8.8.8.8#53 > Dec 2 15:39:36 192 dnsmasq[10951]: using only locally-known addresses > for zmedia.com > Dec 2 15:39:36 192 dnsmasq[10951]: using only locally-known addresses > for zintext.com > Dec 2 15:39:36 192 dnsmasq[10951]: using only locally-known addresses > for zeusclicks.com > Dec 2 15:39:36 192 dnsmasq[10951]: using only locally-known addresses > for zeus.developershed.com > Dec 2 15:39:36 192 dnsmasq[10951]: using only locally-known addresses > for zenzuu.com > Dec 2 15:39:36 192 dnsmasq[10951]: using only locally-known addresses > for zenkreka.com > Dec 2 15:39:36 192 dnsmasq[10951]: using only locally-known addresses > for zencudo.co.uk > Dec 2 15:39:36 192 dnsmasq[10951]: using only locally-known addresses > for zedo.com > Dec 2 15:39:36 192 dnsmasq[10951]: using 2434 more local addresses > > That is completely mysterious to me... Looks like dnsmasq is restarted, getting its uplink servers and then applies local name resolution for a number of domains. This you would find in your dnsmasq configuration. cheers ET -- „Wer von seinem Tag nicht zwei Drittel für sich hat, ist ein Sklave.“ ―Friedrich Nietzsche ------------------------------------------------------------------------ leaf-user mailing list: [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/