When no network connectivity exists dhcpcd goes excessively verbose by logging each attempt to broadcast for an IP address, which can happen every 5-10 seconds. Such a verbosity level should be decreased to prevent from filling the log. Reproducible: Always Steps to Reproduce: 1. Unplug the network cable from eth0 2. Run dhcpcd -t 10 eth0 Actual Results: Attempts to broadcast for an IP address are (sys)logged every 10 seconds, each of which adds 5 lines to the log. Expected Results: There's no need to actually log each failed attempt but only the first one. It's even better to log only changes. When dhcpcd 3.0 or above is run while there is no network connectivity it first times out when broadcasting for an IP address then uses APIPA and forks to the background repeatedly checking for network connectivity and broadcasting for an IP address. It also keeps logging messages to the console log, which can largely increase the log file size. Here are my suggestions: * stop logging after xyz minutes/seconds/hours/whatever or * log connection state changes only. IMHO the best implementation would be to log only connection state changes, e.g. a new automatic address has been set up, link activity change was detected aso. I can imagine, for compatibility reasons, adding an argument to switch to quiet mode but IMHO it'd be safer if dhcpcd changed its behaviour - i.e. stay quiet by default - when forked to the background and log only changes, for instance. It could go verbose if a new switch like -v was specified. Thanks for your work.
This is a good idea, but in practice is quite complicated. Just so you know and don't expect it "soon".
(In reply to comment #1) > This is a good idea, but in practice is quite complicated. Just so you know and > don't expect it "soon". No problem, take the time you need. And if you want me to contribute, I'd be glad.
Patches are always welcome :)
dhcpcd-3.1.8 is in the tree, so fixed.
Hum... You were joking when you said "don't expect it soon", weren't you? ;-) Thanks anyway.
