Skip to content

Commit 29e150f

Browse files
committed
Remove 'cmd not ready' explanation from readme.md
1 parent 6f3c671 commit 29e150f

File tree

1 file changed

+0
-14
lines changed

1 file changed

+0
-14
lines changed

readme.md

Lines changed: 0 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -283,20 +283,6 @@ $ iostat -c 2 -w 5
283283

284284
We align CPU calculation intervals (`-w`) with tmux status bar refresh interval (`status-interval` setting).
285285

286-
### "cmd not ready" message
287-
288-
When you run *tmux* for the first time, you might see following message instead of CPU metric for few seconds.
289-
290-
> cmd ~/.tmux/plugins/sysstat/scripts/cpu.sh not ready
291-
292-
This is because CPU calculation is long running command, which need to measures CPU average per second for specific time interval. It's not a one-shot command, like memory calculation, which just queries `vmstat` or `proc/meminfo` for current system state. If we did the same for CPU calculation, it would have just print CPU usage average since system bootstrap (not for last X seconds).
293-
294-
Quote from `man tmux`:
295-
> When constructing formats, tmux does not wait for `#()' commands to finish; instead, the previous result from running the same command is used, or a placeholder if the command has not been run before. If the command hasn't exited, the most recent line of output will be used, but the status line will not be updated more than once a second.
296-
297-
Therefore, when you run `tmux` for the first time, there is no previous result, thus it prints `<'cmd' not ready>`. Next time status bar is refreshed, tmux will use previous command's output. This is expected behavior.
298-
299-
300286
Internals: memory calculation
301287
----------------------------
302288
You might ask what we treat as `free` memory and how it's calculated.

0 commit comments

Comments
 (0)