On Tue, Aug 6, 2013 at 4:57 PM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Tue, 2013-08-06 at 16:56 +0200, Sedat Dilek wrote: >> On Tue, Aug 6, 2013 at 4:50 PM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: >> > On Tue, 2013-08-06 at 16:46 +0200, Sedat Dilek wrote: >> > >> > Heh, the interesting messages are always cut out of the log: >> > >> > Aug 6 16:30:34 fambox wpa_supplicant[2533]: wlan0: WPA: RX message 1 of 4-Way Handshake from 00:04:0e:e4:00:3d (ver=2) >> > Aug 6 16:30:34 fambox wpa_supplicant[2533]: RSN: msg 1/4 key data - hexdump(len=0): >> > Aug 6 16:30:34 fambox wpa_supplicant[2533]: Get randomness: len=32 entropy=4 >> > Aug 6 16:30:34 fambox wpa_supplicant[2533]: random from os_get_random - hexdump(len=32): [REMOVED] >> > Aug 6 16:30:34 fambox wpa_supplicant[2533]: random_mix_pool - hexdump(len=20): [REMOVED] >> > Aug 6 16:30:34 fambox wpa_supplicant[2533]: random from internal pool - hexdump(len=16): [REMOVED] >> > Aug 6 16:30:34 fambox wpa_supplicant[2533]: random_mix_pool - hexdump(len=20): [REMOVED] >> > Aug 6 16:30:34 fambox rsyslogd-2177: imuxsock begins to drop messages from pid 2533 due to rate-limiting >> > [...] >> > >> >> Do you know how I can workaround the rsyslogd rate-limiting? > > Me? no. > Hmmm, I thought about reducing from -ddd to -d or install a newer rsyslog. - Sedat - > johannes > -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html