2009/11/26 a...@lingnu.com:
looks like the implementation of sysUpTime actually returns
the time passed since the snmp daemon has started:
1. why not return the real system uptime ? (as the MIB name suggests)
Because that's not what the sysUpTime value reports.
See the DESCRIPTION clause
2009/11/26 a...@lingnu.com:
looks like the implementation of sysUpTime actually returns
the time passed since the snmp daemon has started:
1. why not return the real system uptime ? (as the MIB name suggests)
Because that's not what the sysUpTime value reports.
See the DESCRIPTION clause
2009/11/26 a...@lingnu.com:
looks like the implementation of sysUpTime actually returns
the time passed since the snmp daemon has started:
1. why not return the real system uptime ? (as the MIB name suggests)
Because that's not what the sysUpTime value reports.
See the DESCRIPTION clause
2009/11/29 a...@lingnu.com:
the issue could have been resolved by sampling the
system uptime when the snmp daemon starts, and using
it to calculate the sysUptime value, instead of relaying
on the system clock
But the value of system uptime when the agent starts is 0,
by definition.
The SNMP
On Sun, Nov 29, 2009 at 7:39 PM, Dave Shield d.t.shi...@liverpool.ac.ukwrote:
2009/11/29 a...@lingnu.com:
the issue could have been resolved by sampling the
system uptime when the snmp daemon starts, and using
it to calculate the sysUptime value, instead of relaying
on the system clock
looks like the implementation of sysUpTime actually returns
the time passed since the snmp daemon has started:
1. why not return the real system uptime ? (as the MIB name suggests)
2. out specific case:
when our system boots, the time is 'Thu Jan 1 00:00:00 UTC 1970',
and this is the system time
2009/11/26 a...@lingnu.com:
looks like the implementation of sysUpTime actually returns
the time passed since the snmp daemon has started:
1. why not return the real system uptime ? (as the MIB name suggests)
Because that's not what the sysUpTime value reports.
See the DESCRIPTION clause
