Bug #3677
Updated by Junxiao Shi about 7 years ago
Steps to reproduce: 1. start NFD 2. change system clock (manually or with NTP client) 3. execute `nfdc status` `nfd-status -v` Expected: "uptime" field reflects the actual duration NFD has been running Actual: "uptime" field is inaccurate Root cause: nfdc `nfd-status` **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.