On Sat, 09 Oct 2004 12:39:41 -0400 Michael wrote:
MJS> Robert Story (Coders) wrote:
MJS> > On Fri, 08 Oct 2004 19:13:37 -0400 Michael wrote:
MJS> > MJS> 1.APPLIED Wrapped SO_BSDCOMPAT socket option setting from
MJS> > MJS>    snmplib/snmpUDPDomain.c and from
MJS> > MJS>    snmplib/snmpUDPIPv6Domain.c

The question here is, how can we figure out which OS/kernel versions need this,
and which don't. A local uname call is probably the most reasonable quick fix.


MJS> > MJS> 8.APPLIED Wrapped "No MemShared line in /proc/meminfo" in
MJS> > MJS>   agent/mibgroup/ucd-snmp/memory.c
MJS> > MJS>   with netsnmp_os_prematch('Linux', "2.4")
MJS> > 
MJS> > Maybe that should just be moved to a debug message, or removed
MJS> > altogether.

Actually, there is already a partial fix in 5.2. The memory proc file is parsed
once at startup, and any errors are issued then. (5.1 would issue the warning
every time the table was hit). That fix could easily be back-ported, or as I
mentioned, just turn the errors into debug messages. I prefer error messages,
but the users seem to get annoyed at them.


MJS> > MJS> 25.NOT DONE configure.in
MJS> > MJS>    Modify HAVE_SSIZE_T to provide value "1"
MJS> > MJS> 
MJS> > MJS>    Seems low risk and appropriate.  Comments ?
MJS> > 
MJS> > Hmmm... Again, this seems to already have been done. Is there a link
MJS> > where I can see the diff?

I think this is just a stylistic difference. The existing method does define 1.
All this would change would be the comment. And the vast majority of defined in
configure do not specify a value and comment, so I suggest skipping this one.

The dlopen change (also in configure.in) looks reasonable, but makes me
nervous. We've had dlmod detection broken in several releases in the past. I'm
inclined to go with "if it ain't broke, don't fix it."  If someone else wants
to fix/test make sure you try a wide variety of platforms and vendors.  Of
course, if we did want to change it, 5.2 would be as good a place as any, since
first releases almost always have problem to be ironed out.

-- 
Robert Story; NET-SNMP Junkie <http://www.net-snmp.org/>
<irc://irc.freenode.net/#net-snmp>
Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders>

You are lost in a twisty maze of little standards, all different. 


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Net-snmp-coders mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to