BIND 10 #2785: perfdhcp sent/received durations do not appear to be accurate
BIND 10 Development
do-not-reply at isc.org
Wed Feb 20 13:31:43 UTC 2013
#2785: perfdhcp sent/received durations do not appear to be accurate
-------------------------------------+-------------------------------------
Reporter: tmark | Owner:
Type: | Status: new
defect | Milestone: DHCP
Priority: | Outstanding Tasks
medium | Keywords:
Component: | Sensitive: 0
perfdhcp | Sub-Project: DNS
CVSS Scoring: | Estimated Difficulty: 0
Defect Severity: N/A | Total Hours: 0
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
perfdhcp expresses the packet sent and received times in an exchange pair,
ostensibly, as a duration from the epoch. Using
to_iso_string(time_duration) should result in:
HHMMSS.ffffff where it is hours, minutes, seconds. fractional seconds of
the duration, so we should it expressed since the epoch. The actual
values for hours, however is not accurate as can be seen from the
following stdout excerpt:
sent / received: 53746523458.837044 / 53746523458.851693
which is 5374652 hours since the epoch. This value appears to be wrong as
it equates roughly 613 years.
What would be more useful would be expressing the durations as "since
process start time". It would also be helpful to display the packet sent
and/or received as date/time to facilitate correlating these entries to
server side logs/events.
Perhaps:
sent/received (sent timestamp) / (recvd timestamp) diff: (duration
between)
there are any number of alternatives.
--
Ticket URL: <http://bind10.isc.org/ticket/2785>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list