I use code blocks and screen captures in nearly all of my questions hereall of my questions here. Sometimes it's to illustrate a pointillustrate a point. Sometimes it's absolutely criticalabsolutely critical to describing the problem. Very rarely are the contents of such an image necessary for search reasons. Sometimes text is the only appropriate methodtext is the only appropriate method.
I don't see any problem with screenshots. I don't even understand the issue here. It's a strange complaint.
Depending on the problem, the environment, the frequency of the issue and the resources available, a screenshot is sometimes easier to capture. This is especially true in the case of complex terminal output or any form of remote console/KVM/out-of-band management.
More than that, the screenshot is there to illustrate a point-in-time condition. Searchability is a non-issue.
Let's say I'm trying to describe the state of the storage appliance I'm working on... Which looks better?
┌nmon─13g─────────────────────Hostname=san2─────────Refresh= 2secs ───18:40.40───────────────────────────┐
│ CPU Utilisation ───────────────────────────────────────────────────────────────────────────────────────│
│ +-------------------------------------------------+ │
│CPU User% Sys% Wait% Idle|0 |25 |50 |75 100| │
│ 1 0.0 0.0 0.0 100.0| > | │
│ 2 0.0 0.0 0.0 100.0| > | │
│ 3 0.0 0.0 0.0 100.0| > | │
│ 4 0.0 0.0 0.0 100.0| > | │
│ 5 0.0 0.0 0.0 100.0| > | │
│ 6 0.0 0.0 0.0 100.0| > | │
│ 7 0.0 0.0 0.0 100.0| > | │
│ 8 0.0 0.0 0.0 100.0| > | │
│ 9 0.0 0.0 0.0 100.0| > | │
│10 0.0 0.0 0.0 100.0| > | │
│11 3.0 0.5 0.0 96.5|U > | │
│12 0.0 0.0 0.0 100.0| > | │
│13 0.0 0.0 0.0 100.0| > | │
│14 0.0 0.0 0.0 100.0| > | │
│15 0.0 0.0 0.0 100.0| > | │
│16 0.0 0.0 0.0 100.0| > | │
│ +-------------------------------------------------+ │
│Avg 0.2 0.1 0.0 99.7| > | │
│ +-------------------------------------------------+ │
│ Memory Stats ──────────────────────────────────────────────────────────────────────────────────────────│
│ RAM High Low Swap │
│ Total MB 32035.1 -0.0 -0.0 32755.0 │
│ Free MB 6578.1 -0.0 -0.0 32755.0 │
│ Free Percent 20.5% 100.0% 100.0% 100.0% │
│ MB MB MB │
│ Cached= 688.1 Active= 471.5 │
│ Buffers= 71.6 Swapcached= 0.0 Inactive = 601.5 │
│ Dirty = 0.1 Writeback = 0.0 Mapped = 43.2 │
│ Slab = 90.0 Commit_AS = 1607.7 PageTables= 7.9 │
│ Kernel Stats ──────────────────────────────────────────────────────────────────────────────────────────│
│ RunQueue 1 Load Average CPU use since boot time │
│ ContextSwitch 525.2 1 mins 0.22 Uptime Days= 0 Hours= 7 Mins=33 │
│ Forks 5.0 5 mins 0.20 Idle Days= 5 Hours= 0 Mins= 9 │
│ Interrupts 356.3 15 mins 0.28 Average CPU use=-1491.10% │
│ Disk I/O ──/proc/diskstats────mostly in KB/s─────Warning:contains duplicates───────────────────────────│
│DiskName Busy Read Write Xfers Size Peak% Peak-RW InFlight │
│sda 0% 0.0 0.0KB/s 0.0 0.0KB 0% 10.0KB/s 0 │
│sda1 0% 0.0 0.0KB/s 0.0 0.0KB 0% 10.0KB/s 0 │
│sda2 0% 0.0 0.0KB/s 0.0 0.0KB 0% 0.0KB/s 0 │
│sda5 0% 0.0 0.0KB/s 0.0 0.0KB 0% 0.0KB/s 0 │
│sdb 0% 0.0 0.0KB/s 0.0 0.0KB 0% 0.0KB/s 0 │
│sdb1 0% 0.0 0.0KB/s 0.0 0.0KB 0% 0.0KB/s 0 │
│sdb9 0% 0.0 0.0KB/s 0.0 0.0KB 0% 0.0KB/s 0 │
│Totals Read-MB/s=0.0 Writes-MB/s=0.0 Transfers/sec=0.0 │
│────────────────────────────────────────────────────────────────────────────────────────────────────────│
│ │
│ │
│ │
│ │
└────────────────────────────────────────────────────────────────────────────────────────────────────────┘
