Bart Van Assche writes:
> That patch has not been reversed. It works as follows:
> * For Unix platforms neither cygwin nor HAVE_IPHLPAPI_H are defined so
> all MIB-II tables are included.
> * When building Net-SNMP with Visual Studio, the Microsoft platform SDK
> or with MinGW then HAVE_IPHLPAPI_
"Bob O'Neil" writes:
> What is the status of the project in terms of thread safety now and
> into the future?
Now, the v1/v2c code is thread safe. See the README.thread file for how
to utilize it. The v3 code and the agent code isn't, and someone would
need to do that work, or sponsor it at le
On 12/01/14 19:38, Wes Hardaker wrote:
> Bart Van Assche writes:
>
>> With the latest Cygwin version must be included before
>> . However, is incompatible with the Cygwin
>> socket header files. Hence disable the mibII MIBs that depend on
>> if needs .
>
> Was that patch reversed?
>
> Based on
Rajkumar Purohit writes:
> can we use vacm_parse_rocommunity(const char *token, char *confline)
> in linux environment ?
Yes!
--
Wes Hardaker
Please mail all replies to net-snmp-coders@lists.sourceforge.net
--
Download
Bart Van Assche writes:
> See also http://sourceforge.net/p/net-snmp/feature-requests/181/
>
> This is a modified version of a patch supplied by jbree...@users.sf.net -
> the whitespace changes have been left out.
-1 actually... That seems like something that is too late for a
release-candidate
Bart Van Assche writes:
> With the latest Cygwin version must be included before
> . However, is incompatible with the Cygwin
> socket header files. Hence disable the mibII MIBs that depend on
> if needs .
Was that patch reversed?
Based on the paragraph above, I believe it was. If it was r
