Project

General

Profile

Actions
Copy link

Bug #3677

open

nfdc status reports wrong uptime if system clock has been changed

Added by Junxiao Shi over 8 years ago. Updated about 7 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Tools
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
3.00 h

Description

Steps to reproduce:

  1. start NFD
  2. change system clock (manually or with NTP client)
  3. execute nfdc status

Expected: "uptime" field reflects the actual duration NFD has been running

Actual: "uptime" field is inaccurate

Root cause: nfdc calculates uptime by subtracting NFD start timestamp from current timestamp.
Since both timestamps are based on system clock, changing the system clock results in inaccurate uptime.

Actions
Copy link
 #1

Updated by Junxiao Shi over 8 years ago

This is an actual bug, because UNIX uptime command could report correct uptime even if system clock has been changed.

To fix this bug, we'll have to measure uptime by steady_clock on NFD side, and expose it through ForwarderStatus general status dataset.

Actions
Copy link
 #2

Updated by Junxiao Shi about 7 years ago

  • Subject changed from nfd-status reports wrong uptime if system clock has been changed to nfdc status reports wrong uptime if system clock has been changed
  • Description updated (diff)
  • Start date deleted (07/18/2016)
Actions
Copy link

Also available in: Atom PDF