On 29.05.06 Thomas Anders ([EMAIL PROTECTED]) wrote:
> Hilmar Preusse wrote:

Hi,

> >[EMAIL PROTECTED]:~ $ snmpget -v2c -c public 127.0.0.1:161 .1.3.6.1.2.1.1.2.0
> >SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::dod.0.0.0.0.0.0.0
> >
> >. I've rebuilt the package from the sources and got the same result.
> >The configure options of the package do not manipulate the
> >sysObjectID. So this can be either:
> >
> >- a broken patch in the Debian package, or
> >- an upstream bug.
> >
> >As we see the same behavior on FreeBSD, I guess the latter is the case.
> 
> We've never had any reports on such behaviour when built from the
> official sources,
> 
Well, I built 5.1.2 from the sources and found the OID to be OK. Then
I did for 5.2.2 using the Debian sources. As the diff.gz does not
manipulate the sysObjectID.0 neither using a patch nor by the
configure options and I saw the same problem on FreeBSD I strongly
believe this to be an upstream bug.


> so may I suggest you get latest 5.3.1.pre3 and make a simple test:
> 
I'll do so, but not before Tuesday as I'm oofline till then.

> BTW, what's the ./config.guess output on your GNU Hurd box?
> 
I do not have a GNU Hurd box and never had.

H.
-- 
sigmentation fault


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to