> > Anyone seen sysctl -a loop forever? I haven't been able to track > > down the MIB that it's gettinng hung up on, but it looks like > > there's a flaw in the algo that is walking through the MIBs. > > Given that this halts the machine while trying to collect entropy > > (sysctl -a is used to help feed /dev/random) at system start up, I > > think it's something worth addressing or pointing out. -sc > > I've observed this when e.g. I had too many nmbclusters configured, > ie when vm.kvm_free was too low (0 in my case :)
Ah, hrm, I think you're onto something here. I haven't played with vm.kvm_free, but I do run with 65536 mbuf clusters. Hrm... this is outside of my expertise. I have 4.X boxes running with 130K mbuf clusters (and I actually need to find a way to increase this further!) so this is definately something I'll run into and likely others will when they update their production boxen. Is this a sysctl data presentation issue? -sc -- Sean Chittenden To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
