Commit 3b64b38
doc: os.uptime() temporary bug notice
Makes it clear that os.uptime() is unreliable in some virtualization
cases.
PR-URL: #36503
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
Reviewed-By: Franziska Hinkelmann <franziska.hinkelmann@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>1 parent da49624 commit 3b64b38
1 file changed
Lines changed: 12 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -368,6 +368,18 @@ changes: | |||
| 368 | 368 | ||
| 369 | 369 | Returns the system uptime in number of seconds. | |
| 370 | 370 | ||
| 371 | + The value returned can be inaccurate in some | ||
| 372 | + rare virtualization cases. The issue arises when the virtualized | ||
| 373 | + guest instance shares the kernel with the host system. | ||
| 374 | + Due to the fact that libuv uses a syscall that | ||
| 375 | + provides host's uptime instead of guest's | ||
| 376 | + uptime on OpenVZ, `os.uptime()` may also provide | ||
| 377 | + erroneous result. | ||
| 378 | + | ||
| 379 | + Please refer to <https://github.com/nodejs/node/issues/36244> and | ||
| 380 | + <https://github.com/libuv/libuv/issues/3068> for an exploration of | ||
| 381 | + this issue, until it is resolved by libuv. | ||
| 382 | + | ||
| 371 | 383 | ## `os.userInfo([options])` | |
| 372 | 384 | <!-- YAML | |
| 373 | 385 | added: v6.0.0 | |
0 commit comments