Cool. -----Original Message----- From: Scott Ullrich [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 4:07 PM To: support@pfsense.com Subject: Re: [pfSense Support] CPU Mib
Thast what I am planningon doing if it works (ship currents bsnmpd) On 1/17/06, Fleming, John (ZeroChaos) <[EMAIL PROTECTED]> wrote: > Just so we're clear, it need to stay in the pfSense builds unless you > start using bsnmp head. :) > > -----Original Message----- > From: Scott Ullrich [mailto:[EMAIL PROTECTED] > Sent: Tuesday, January 17, 2006 3:46 PM > To: support@pfsense.com > Subject: Re: [pfSense Support] CPU Mib > > Doh. Let me mark that out. > > > On 1/17/06, Fleming, John (ZeroChaos) <[EMAIL PROTECTED]> wrote: > > Oh btw my community patch is in head so it shouldn't be needed. > > > > -----Original Message----- > > From: Scott Ullrich [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, January 17, 2006 3:42 PM > > To: support@pfsense.com > > Subject: Re: [pfSense Support] CPU Mib > > > > Sure. I'm testing building bsnmpd from -current now. > > > > On 1/17/06, Fleming, John (ZeroChaos) <[EMAIL PROTECTED]> > wrote: > > > My thoughts are no unless we control when we do checkouts, meaning > we > > > keep a private bsnmp tree and somehow add it to the fbsd tree when > we > > > kick off a buildworld. My feeling is the vendor tree is sort of like > > > tracking current, where it could be broken at any point in time. > > > > > > What do you think? > > > > > > -----Original Message----- > > > From: Scott Ullrich [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, January 17, 2006 2:11 PM > > > To: support@pfsense.com > > > Subject: Re: [pfSense Support] CPU Mib > > > > > > Should we be using this "vendor" tree of theirs instead? > > > > > > On 1/17/06, Fleming, John (ZeroChaos) <[EMAIL PROTECTED]> > > wrote: > > > > Yea, I need to follow up on that. I think Harti addressed the > > > buildworld > > > > issues, but I'm not sure. I recall there were some fixes added > when > > he > > > > imported it to his bsnmp vendor tree. > > > > > > > > -----Original Message----- > > > > From: Scott Ullrich [mailto:[EMAIL PROTECTED] > > > > Sent: Tuesday, January 17, 2006 1:59 PM > > > > To: support@pfsense.com > > > > Subject: Re: [pfSense Support] CPU Mib > > > > > > > > In addition the SoC patches was crashing our build so we backed > them > > > > out. > > > > > > > > On 1/17/06, Fleming, John (ZeroChaos) <[EMAIL PROTECTED]> > > > wrote: > > > > > > > > > > > > > > > > > > > > This has been added to the next version of bsnmp from what I > > > > understand (see > > > > > Sumer of Code patches for bsnmp) but the new version of bsnmpd > > > hasn't > > > > been > > > > > released yet. I also don't have a ETA. > > > > > > > > > > > > > > > > > > > > ________________________________ > > > > > > > > > > > > > > > From: John Cianfarani [mailto:[EMAIL PROTECTED] > > > > > Sent: Monday, January 16, 2006 7:01 PM > > > > > To: support@pfsense.com > > > > > Subject: [pfSense Support] CPU Mib > > > > > > > > > > > > > > > > > > > > Is there a mib for polling CPU on pfsense, I went through the > > entire > > > > walk > > > > > and tried some of the standard ones but couldn't find it. > > > > > > > > > > > > > > > > > > > > John > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
