On Tue, 2008-06-24 at 10:52 +0800, Paul wrote:
> Hi,
>  
> I have two questions:
>  
> Question 1:
>  
> If I use following command in ./configure phase, evreythins works
> fine.
> ./configure --prefix=/not/usr/ --with-install-prefix=/tmp
>  
> But if I use following command in ./configure phase, scalars of
> myself's dynamic loadable module will response with "GENERIC
> ERROR" (In mib browser, it also shows "error index: 0".).
> ./configure --disable-debugging --enable-mini-agent
> --with-transports=UDP --with-mib-modules=ucd-snmp/dlmod
> --with-out-mib-modules=mibII/system_mib --prefix=/not/usr/
> --with-install-prefix=/tmp
>  
> I really have no idea about this condition. Could anyone give me a
> hint to check out what's the problem? Thanks.

Yes.

You need to learn how to use a compiler and a linker. Since you seem to
be at a school they should be able to teach you that, probably in a
course named 'Introduction to C programming' or something like that.
 
> Question 2:
>  
> If I use following command in ./configure phase, default
> mibII/system_mib should also be included in agent.
> ./configure --prefix=/not/usr/ --with-install-prefix=/tmp
>  
> But I implement a new mibII/system_mib module by myself and dynamic
> load it, the agent still works fine.
> When I send a system get request(ex: get sysDescr.0), it will response
> with the correct answer from my new mibII/system_mib module.
> There seems no conflicts.  Could anyone tell me why? Why there is no
> conflict? Why duplicate registrations have no bad effect? Thanks.

I have already answered this exact question.
Please read the list archives.

/MF
> 


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to