>> Date: Mon, 17 Feb 2014 11:22:27 +0000 >> From: Stuart Henderson <[email protected]> >> >> On 2014/02/17 09:35, Philipp wrote: >> > Am 17.02.2014 09:22 schrieb Alex Mathiasen: >> > >Thank you! This solved my problem. >> > >> > Cheers.. found the hard way the other day. >> > >> > There should really be some dmesg when state-tables overflow. >> > This "silent" dropping is wasting time in debugging such situations. >> > >> > Sorry for talk instead of diff :-} >> > >> >> Writing messages that show up in dmesg is not cheap, particularly >> on systems with serial console. > >You'd obviously have to rate limit these somehow. See ratecheck(9).
No, the original answer here is the right one. dmesg is not a place to print transient information. It is supposed to supply configuration information, not turn into a cesspool of spam.
