-Coders,
one of the CVS commits (mostly Coverity fixes) within the last two days
managed to break all three MAIN/V5-3-patches/V5-2-patches major CVS
lines. It still builds for me on Linux/x86, but make test only has
39/58 (MAIN), 37/58 (5.3.1.dev) and 33/46 (5.2.2.dev) success scores.
On Fri, 10 Mar 2006 12:29:24 +0100, Thomas Anders [EMAIL PROTECTED]
said:
Thomas one of the CVS commits (mostly Coverity fixes) within the last
Thomas two days managed to break all three
Thomas MAIN/V5-3-patches/V5-2-patches major CVS lines. It still
Thomas builds for me on Linux/x86, but make
On Thu, 9 Mar 2006 13:45:19 +0100, Le Gall Jean-Patrick (Skysoft ATM)
[EMAIL PROTECTED] said:
Le I've try to use mib2c.scalar.conf, but it don't seems to work.
That's not for tables (arrays). That won't work
Le I've try to look for a netSnmpArray management, but it seems really
Le
On Wed, 08 Mar 2006 15:40:15 +, Dave Shield [EMAIL PROTECTED] said:
While we are at discussing 5.1.x, how are we going to deal with
the Coverity bugs and 5.1.x (and 5.0.x)?
Dave My gut reaction is to say that the Coverity bugs should be
Dave considered w.r.t 5.2.x and above. The 5.1.x
I would like a mechanism to check the connection to
the master agent. For example the master crashes and
then up again. How can I make sure that my subagent
reconnect properly to the master??? Do I have to do
these steps again:
On Fri, 10 Mar 2006 06:35:38 -0800, Wes Hardaker [EMAIL PROTECTED] said:
Thomas Anyone else seeing this? Ideas? (I haven't had the chance yet
Thomas to look into the details.)
Wes Yeah, I saw it very late last night. Then when zzz
Fixed...
Summary: 59 / 59 succeeded.
--
Wes Hardaker
Quoting Wes Hardaker [EMAIL PROTECTED]:
I thought we actually had agreed ... that 5.1.4 would be the last...
If I'm wrong ...
and people think it's the wrong choice, then lets
decide that *before* I say that in the formal announcement.
No - I think it's the right time to close down 5.1.x.
