New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Produce too much log #124
Comments
I use systemd's |
@felixonmars in fact journald will be more affected, because it shares the limit among all the logs. With syslog, it's easier to filter out and rotate dnsmasq's logs so it won't occupy too much space. |
I didn't get any response from dnsmasq-discuss. Here is how to discard these logs with rsyslog: In
There doesn't seem to be an easy way to filter logs in journald though. |
Simon Kelley has fixed it in dnsmasq(link). Closing. |
Thanks for the update! |
Dnsmasq logs every entry in the list every time it starts/reloads, thus created an
/var/log/syslog
as large as 0.5GiB on my router.Users should be warned of this problem.
There is unfortunately no easy fix. Maybe we should contact
dnsmasq-discuss.
The text was updated successfully, but these errors were encountered: