Bump sched buckets to 256 (was 0)

[Johny01]

Hi

Can anyone explain what does Bump sched buckets 256 (was 0) really means.  I just upgrade my existing pfsense 2.0.3 to pfsense 2.2 . One thnig that I noticed , the console changed to "Bump sched bucket 256 ( was 0) " . Before upgrade it was " Bump sched buckets 64 (was 0) "

thanks for tips and assistance

[jimp]

It's harmless. It's found when using limiters (or captive portal with per-user bandwidth limits).

[phil.davis]

This gets asked about every few months. It should not be necessary for normally running code to spam the console and system log like this, just to tell us such an interesting thing ;)
IMHO it would be good to look at where this message is generated and see if it should be totally suppressed, or only reported when something is "odd".

[doktornotor]

@phil.davis:

It should not be necessary for normally running code to spam the console and system log like this, just to tell us such an interesting thing ;)
IMHO it would be good to look at where this message is generated and see if it should be totally suppressed

Amen. I also "love" logspam like "hostapd: ath0_wlan0: WPA rekeying GTK"

[ipfftw]

Had same prob after i replaced the motherboard in my machine. Following this it was resolved:

Firewall-> Traffic Shaper-> Limiter -> (select a limiter) -> advanced button -> set yo bucket to 256

do it a bunch more times if you have a bunch more limiters.

not sure what the effect would be. I would hope that pfsense could manage its own damn buckets and not bother me about it if it truly is harmless.

https://forum.pfsense.org/index.php?topic=69506.0