RE: question about net-snmp
"Mike Ayers" <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <83E753BE7B6A324ABB336245BAF1DAAC06F830DB@mailserver.metatv-ds.metatv.com> |
> From: [email protected] > [mailto:[email protected]] On > Behalf Of Brian A. Seklecki > are we talking about time_t being a 64bit integer ? No. The year 2038 problem occurs with 32 bit integers which count seconds and start in 1970. SNMP uses a 32 bit timestamp, but it is referenced only from when the engine is booted, so v1 and v2c engines do not suffer from the year 2038 problem, but must be rebooted at least once every 68 years. SNMPv3 introduced a 31 bit engine boot counter which extends the potential uptime without reboot significantly. Yes, sad to say, SNMPv3 suffers from the year 146,135,513,385 problem. Will we ever learn? HTH, Mike ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users