With NetSNMP as a client and SNMP Research as a server, we've noticed
out-of-time window errors on the client side after large abrupt
(negative) time changes. Both client and server run on the same
machine. If someone changes the system date backward by, say 3 days,
NetSNMP can no longer talk to the server. In thinking about this,
doesn't it make sense for NetSNMP to calculate engine time from the
CLOCK_MONOTONIC clock (if available)? That clock completely isolates
one from a user's capricious clock change. Just a thought ...
-Mike Ferrara
[EMAIL PROTECTED]
PS - I've verified this problem with NetSNMP 5.0.8 - 5.2.0 using
perl-NetSNMP
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
